Kamlapati Choubey

A use-after-free issue exists in the way Foxit Reader handles 3D annotations. This can be triggered by a specially crafted Javascript code inside a malicious PDF document, leading to memory corruption and potentially allowing an attacker to execute arbitrary code. An attacker needs to trick the user into opening the malicious file to trigger this issue. Exploitation is also possible if a user visits a specially crafted, malicious site when the browser plugin extension is enabled.

A code execution issue exists in the Javascript saveAs API of Foxit Reader. This is due to the improper handling of specially crafted malformed files, which can lead to the creation of arbitrary files and potentially result in remote code execution. An attacker must trick the user into opening a malicious file to exploit this issue. Additionally, exploitation is possible if a user visits a specially crafted malicious site when the browser plugin extension is enabled.

The issue is related to errors in processing hyperlinks and mistreatment of whitespace characters in the Javascript exportDataObject API. This can allow a remote attacker to execute arbitrary code. A specially crafted malicious file can create files at arbitrary locations, leading to code execution. Exploitation is possible if a user opens the malicious file or visits a specially crafted site with the browser plugin extension enabled.

The issue is related to a type confusion vulnerability in the way Foxit Reader handles field value properties. This can be triggered by a specially crafted Javascript code inside a malicious PDF document, leading to memory corruption and potentially allowing an attacker to execute arbitrary code. An attacker can exploit this by tricking a user into opening a malicious file or by having the user visit a specially crafted malicious site if the browser plugin extension is enabled.

The issue is related to the exportDataObject API in Foxit Reader, which fails to properly validate a dangerous extension, leading to an arbitrary file creation vulnerability. This can allow an attacker to create files at arbitrary locations, potentially resulting in arbitrary code execution. The exploitation can occur if a user opens a specially crafted malicious file or visits a malicious site with the browser plugin extension enabled.

The issue is related to a Use After Free vulnerability that could result in arbitrary code execution in the context of the current user. Exploitation of this issue requires user interaction, where a victim must open a malicious file. This allows an attacker to execute arbitrary code.

A use-after-free vulnerability exists in the JavaScript engine of Foxit Software’s PDF Reader. By prematurely deleting objects associated with pages, a specially crafted PDF document can trigger the reuse of previously freed memory, which can lead to arbitrary code execution. An attacker needs to trick the user into opening the malicious file to trigger this vulnerability. Exploitation is also possible if a user visits a specially crafted, malicious site if the browser plugin extension is enabled.

A use-after-free vulnerability exists in the way Foxit Reader handles destroying annotations. Specially crafted Javascript code inside a malicious PDF document can trigger reuse of a previously freed object, which can lead to memory corruption and result in arbitrary code execution. An attacker needs to trick the user into opening the malicious file to trigger this vulnerability. Exploitation is also possible if a user visits a specially crafted, malicious site if the browser plugin extension is enabled.

A use-after-free vulnerability exists in the JavaScript engine of Foxit Software’s PDF Reader. By prematurely deleting objects associated with pages, a specially crafted PDF document can trigger the reuse of previously freed memory, which can lead to arbitrary code execution. An attacker needs to trick the user into opening the malicious file to trigger this vulnerability. Exploitation is also possible if a user visits a specially crafted, malicious site if the browser plugin extension is enabled.

A type confusion vulnerability exists in the Javascript `checkThisBox` method. Specially crafted Javascript code inside a malicious PDF document can cause memory corruption and lead to remote code execution. The user would need to open a malicious file to trigger the issue. The vulnerability can be exploited by a remote attacker using a specially created PDF file.

The issue is related to a lack of protection for sensitive data in the Windows GDI component, allowing an attacker to disclose protected information using a specially crafted document. This can enable attackers to obtain sensitive information and affect the system.

The issue is related to an information disclosure vulnerability in the Windows GDI component, which improperly discloses the contents of its memory. This can be exploited by attackers to obtain sensitive information using a specially crafted document. The vulnerability is associated with errors in the mechanisms for handling objects in memory.

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 the `subject` property of `Annotation` 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.

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 the `createIcon` method of an `app` object, resulting from the lack of validation of an object's existence prior to performing operations on it. An attacker can leverage this to execute code in the context of the current process.

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 the `delay` property of `Annotation` objects, resulting from 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.

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 the `attachIcon` property of `Annotation` 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.