Carsten Book

The issue is related to a buffer data boundary operation overflow. It may allow a remote attacker to execute arbitrary code. Memory safety bugs were reported, showing evidence of memory corruption, which could potentially be exploited.

The issue is related to memory safety bugs, including evidence of memory corruption, which could potentially be exploited to run arbitrary code. The vulnerability is associated with a buffer overflow in memory, allowing a remote attacker to execute arbitrary code.

Memory safety bugs were reported, showing evidence of memory corruption. It is presumed that with enough effort, some of these bugs could be exploited to run arbitrary code.

Memory safety bugs were reported, showing evidence of memory corruption. It is presumed that with enough effort, some of these bugs could be exploited to run arbitrary code.

Memory safety bugs were reported, showing evidence of memory corruption. It is presumed that with enough effort, some of these bugs could be exploited to run arbitrary code.

The issue affects the browser engine, allowing remote attackers to cause a denial of service, which may result in memory corruption and application crash, or possibly execute arbitrary code via unknown vectors.

A remote code execution issue exists due to the incorrect parsing of specific font types by Microsoft Windows and Microsoft Office. This could allow an attacker to execute arbitrary code via a crafted web site or Office document. An attacker who successfully exploits this issue could run arbitrary code as the logged-on user.

The issue arises from improper handling of pointers, allowing remote attackers to execute arbitrary code or cause a denial of service due to memory corruption and framework outage via a crafted web site.

The issue allows remote attackers to cause a denial of service, resulting in memory corruption and application crash, and possibly execute arbitrary code. This is related to vectors involving layout/generic/nsBlockFrame.cpp and the ` evaluate` function in modules/plugin/base/src/nsNPAPIPlugin.cpp.

The issue is related to multiple unspecified vulnerabilities in the browser engine, which can be exploited by remote attackers to cause a denial of service, resulting in memory corruption and application crash, or possibly execute arbitrary code via unknown vectors.

The issue is related to the handling of first-letter frames in the browser engine. Remote attackers can cause a denial of service, resulting in memory corruption and application crash, or possibly execute arbitrary code via unspecified vectors.

Name of the Vulnerable Software and Affected Versions: Mozilla Firefox versions 3.5.x through 3.5.2 Description: The issue is related to an unspecified vulnerability in the JavaScript engine, which can be exploited by remote attackers to cause a denial of service, resulting in memory corruption and application crash, or possibly execute arbitrary code via unknown vectors. Recommendations: For Mozilla Firefox versions 3.5.x through 3.5.2, update to version 3.5.3 or later to resolve the issue.

Name of the Vulnerable Software and Affected Versions: Mozilla Firefox versions prior to 3.0.14 Mozilla Firefox versions 3.5.x prior to 3.5.2 Thunderbird versions prior to 2.0.0.24 SeaMonkey versions prior to 1.1.19 Description: The issue is related to multiple unspecified vulnerabilities in the JavaScript engine. These vulnerabilities can be exploited by remote attackers to cause a denial of service, resulting in memory corruption and application crash, or possibly execute arbitrary code. The vulnerabilities are related to the use of mutable strings in the `js StringReplaceHelper` function in `js/src/jsstr.cpp`. Recommendations: For Mozilla Firefox versions prior to 3.0.14, update to version 3.0.14 or later. For Mozilla Firefox versions 3.5.x prior to 3.5.2, update to version 3.5.2 or later. For Thunderbird versions prior to 2.0.0.24, update to version 2.0.0.24 or later. For SeaMonkey versions prior to 1.1.19, update to version 1.1.19 or later.

The issue allows remote attackers to cause a denial of service (crash) and possibly trigger memory corruption via certain vectors, including large switch statements, specific uses of `watch` and `eval`, and certain uses of the `mousedown` event listener.