The remote host has been observed running a version of Foxit Reader that is subject to multiple attack vectors.
Description
Versions of Foxit Reader prior to 8.2.1 are affected by the following vulnerabilities : - Multiple use-after-free errors exist that are triggered as user-supplied input is not properly validated. With a specially crafted file, a context-dependent attacker can dereference already freed memory and potentially execute arbitrary code. - Multiple type confusion errors exist that are triggered as user-supplied input is not properly validated. With a specially crafted file, a context-dependent attacker can potentially execute arbitrary code. - Multiple unspecified out-of-bounds access flaws exist. These flaws may allow a context-dependent attacker to disclose memory contents or potentially execute arbitrary code. - A flaw exists that is triggered as certain input is not properly validated. This may allow a context-dependent attacker to corrupt memory and potentially execute arbitrary code. - A a NULL pointer dereference error exists that is triggered when handling a specially crafted PDF file. This may allow a context-dependent attacker to cause the program to crash. - An out-of-bounds read flaw exists that is triggered when handling specially crafted fonts in PDF files. This may allow a context-dependent attacker to potentially disclose sensitive information. - An out-of-bounds read flaw exists that is triggered when handling specially crafted PDF files. This may allow a context-dependent attacker to potentially disclose sensitive information. - An out-of-bounds access flaw exists that is triggered when handling specially crafted Pattern objects. This may allow a context-dependent attacker to potentially execute arbitrary code. - An out-of-bounds access flaw exists that is triggered when handling specially crafted XFA forms. This may allow a context-dependent attacker to potentially execute arbitrary code. - An out-of-bounds access flaw exists that is triggered when handling specially crafted ePub files. This may allow a context-dependent attacker to potentially execute arbitrary code. - An out-of-bounds read flaw exists that is triggered when handling specially crafted JPEG2000 files. This may allow a context-dependent attacker to potentially disclose sensitive information. - An out-of-bounds read flaw exists that is triggered when handling specially crafted PDF files. This may allow a context-dependent attacker to potentially disclose sensitive information. - A use-after-free error exists. The issue is triggered by a failure to validate the existence of an object before performing operations on it. This may allow a context-dependent attacker to use a specially crafted Xref object to dereference already freed memory and potentially execute arbitrary code. - A use-after-free error exists in the 'execMenuItem()' function. The issue is triggered by a failure to validate the existence of an object before performing operations on it. This may allow a context-dependent attacker to dereference already freed memory and potentially execute arbitrary code. - A use-after-free error exists in the 'deleteItemAt()' method. The issue is triggered by a failure to validate the existence of an object before performing operations on it. This may allow a context-dependent attacker to dereference already freed memory and potentially execute arbitrary code. - A use-after-free error exists in the 'openDoc()' method. The issue is triggered by a failure to validate the existence of an object before performing operations on it. This may allow a context-dependent attacker to dereference already freed memory and potentially execute arbitrary code. - A use-after-free error exists. The issue is triggered by a failure to validate the existence of an object before performing operations on it. This may allow a context-dependent attacker to use a specially crafted ePub file to dereference already freed memory and potentially execute arbitrary code. - A use-after-free error exists in the 'buttonGetIcon()' method. The issue is triggered by a failure to validate the existence of an object before performing operations on it. This may allow a context-dependent attacker to dereference already freed memory and potentially execute arbitrary code.