Q1Iq

تتعلق المشكلة بإدارة الذاكرة المحسّنة وقد تؤدي إلى حدوث حالة «رفض الخدمة» عند معالجة محتوى الويب. وترتبط هذه المشكلة بتخصيص موارد غير محدود، وهو ما يمكن أن يستغله مهاجم عن بُعد للتسبب في حالة «رفض الخدمة».

A segmentation fault was discovered in WebAssembly via the component wabt::Decompiler::WrapChild.

A heap overflow issue was discovered in WebAssembly via the wabt::Node::operator() component.

The issue is related to an abort in `CWriter::MangleType()`. No information is provided about the estimated number of potentially affected devices or real-world incidents where this issue was exploited.

A segmentation fault was discovered in WebAssembly via the component wabt::cat compute size.

A segmentation fault was discovered in radare2 via the component wasm dis at p/wasm/wasm.c.

The issue is related to a segmentation violation via the `njs scope valid value` function at `njs scope.h`. This could potentially allow a remote attacker to cause a denial of service. The vendor disputes the significance of this report, stating that NJS does not operate on untrusted input.

The issue is related to an out-of-bounds read in the `OnReturnCallExpr` component, specifically via the `GetReturnCallDropKeepCount` method.

A heap overflow issue was discovered in the `std::vector` component, specifically via `std::vector<wabt::Type, std::allocator<wabt::Type>>::size()` at `/bits/stl vector.h`.

The issue is related to an out-of-bounds read in the `OnReturnCallIndirectExpr` component, specifically via the `GetReturnCallDropKeepCount` method.

An issue was discovered in wasm2c, where an abort occurs in the CWriter::Write function.

The issue is related to a heap-use-after-free bug caused by an illegal memory copy in the `njs json parse iterator call` function at `njs json.c`. This bug can be exploited by a remote attacker to execute arbitrary code.

A memory corruption issue was addressed with improved validation. Processing maliciously crafted web content may lead to arbitrary code execution. The issue is related to a buffer overflow in WPE WebKit and WebKitGTK modules, which can be exploited by a remote attacker to access confidential data, compromise data integrity, and cause a denial of service.

The issue is related to a segmentation violation in the `njs string offset` function at `src/njs string.c`. This can lead to an uncontrolled resource consumption. An attacker, acting remotely, may exploit this issue to elevate their privileges.

The issue is related to the function `njs array convert to slow array` at `src/njs array.c` in the Nginx NJS interpreter, which can lead to uncontrolled resource consumption. This can potentially allow a remote attacker to elevate their privileges. The problem is caused by a segmentation violation in the mentioned function.

The issue is related to a segmentation violation via the `njs lvlhsh bucket find()` function at `njs lvlhsh.c` in the Nginx NJS interpreter. This can lead to an uncontrolled resource consumption, potentially allowing a remote attacker to cause a denial of service.

The issue is related to an out-of-bounds read via the `fxUint8Getter` function at `/moddable/xs/sources/xsDataView.c`.

The issue is related to a segmentation violation in the `njs vmcode interpreter` function at `src/njs vmcode.c`. This can lead to an uncontrolled resource consumption. An attacker could potentially exploit this to cause a denial of service.

A stack buffer overflow issue was discovered in Espruino via the `jsvNewFromString` function in `src/jsvar.c`.

A stack buffer overflow issue was discovered in Espruino via the src/jsvar.c file, specifically in the jsvGetNextSibling function.