Ashfaq Ansari

This issue allows remote attackers to execute arbitrary code on affected installations. User interaction is required, where the target must visit a malicious page or open a malicious file. The flaw exists within the handling of `Doc` objects due to the lack of validating the existence of an object prior to performing operations on it. An attacker can leverage this to execute code in the context of the current process. It may also lead to information disclosure or remote code execution through potential Use-After-Free or Out-of-Bounds Read vulnerabilities when handling certain JavaScripts, `Doc` objects, or AcroForms.

This issue allows remote attackers to disclose sensitive information on affected installations. User interaction is required, where the target must visit a malicious page or open a malicious file. The flaw exists within the handling of `Doc` objects due to the lack of validating the existence of an object prior to performing operations on it. An attacker can leverage this, in conjunction with other issues, to execute arbitrary code in the context of the current process.

The issue is related to a memory corruption problem, specifically a use-after-free error, which may lead to arbitrary code execution. This can be exploited by a remote attacker to execute arbitrary code.

A remote code execution issue exists due to the scripting engine's handling of objects in memory. This could lead to memory corruption, allowing an attacker to execute arbitrary code in the context of the current user. If the user has administrative rights, the attacker could gain control of the system, enabling them to install programs, view, change, or delete data, or create new accounts with full user rights.

This issue allows remote attackers to execute arbitrary code on vulnerable installations. User interaction is required, where the target must visit a malicious page or open a malicious file. The flaw exists within the handling of `CPDF Object` objects due to the lack of validating the existence of an object prior to performing operations on it. An attacker can leverage this to execute code under the context of the current process.

This issue allows remote attackers to disclose sensitive information on vulnerable installations. User interaction is required, where the target must visit a malicious page or open a malicious file. The flaw exists within the parsing of PDF documents due to the lack of proper validation of user-supplied data. This can result in a read past the end of an allocated object, potentially allowing an attacker to execute code in the context of the current process when combined with other vulnerabilities.

This issue allows remote attackers to disclose sensitive information on vulnerable installations. User interaction is required, where the target must visit a malicious page or open a malicious file. The flaw exists within the parsing of `ObjStm` objects due to the lack of proper validation of user-supplied data, resulting in a read past the end of an allocated object. An attacker can leverage this, in conjunction with other issues, to execute arbitrary code in the context of the current process.

This issue allows remote attackers to disclose sensitive information on vulnerable installations. User interaction is required, where the target must visit a malicious page or open a malicious file. The flaw exists within the parsing of PDF files due to the lack of proper validation of user-supplied data, resulting in a read past the end of an allocated object. An attacker can leverage this, in conjunction with other issues, to execute code in the context of the current process.

This issue allows remote attackers to disclose sensitive information on vulnerable installations. User interaction is required, where the target must visit a malicious page or open a malicious file. The flaw exists within the parsing of PDF files due to the lack of proper validation of user-supplied data, resulting in a read past the end of an allocated object. An attacker can leverage this, in conjunction with other issues, to execute code in the context of the current process.

The issue is caused by a buffer overflow in memory, which can be exploited by a remote attacker using a specially crafted Mach-O file. This can lead to memory corruption.

The issue is related to memory corruption that occurs when parsing a malformed Mach-O file. This can be exploited by a remote attacker to cause memory damage. The vulnerability is caused by a buffer overflow operation in memory.

The issue is caused by a buffer overflow in the dynamic memory due to insufficient validation of the `dwCompressionSize` parameter in the Microsoft WIM (WIMHEADER V1 PACKED) file header. This can allow a remote attacker to elevate privileges and execute arbitrary code, potentially leading to Remote Code Execution as well as Privilege Escalation.

The issue allows remote attackers to obtain sensitive information or possibly execute arbitrary code via a crafted font in a PDF document.

The issue is related to a stack-based buffer overflow that can be triggered by a crafted LC UNIXTHREAD.cmdsize field in a Mach-O file. This occurs when the file is mishandled during a Security Scan operation, also known as a Custom Scan. This can allow remote attackers to execute arbitrary code.

The issue is related to the improper disclosure of the contents of Internet Explorer's memory, allowing remote attackers to obtain sensitive information from process memory via a crafted web site. This can provide an attacker with information to further compromise the user's system. The vulnerability is associated with the lack of protection for service data.