7 matches found
Adobe Acrobat < 10.1.2 / 9.5 Multiple Vulnerabilities (APSB12-01)
The version of Adobe Acrobat installed on the remote host is earlier than 10.1.2 / 9.5, and therefore affected by multiple memory corruption vulnerabilities. An attacker could exploit these issues by tricking a user into opening a maliciously crafted Acrobat file, resulting in arbitrary code...
CVE-2011-4370
Adobe Reader and Acrobat before 9.5, and 10.x before 10.1.2, on Windows and Mac OS X allow attackers to execute arbitrary code or cause a denial of service memory corruption via unspecified vectors, a different vulnerability than CVE-2011-4372 and CVE-2011-4373...
CVE-2011-4370
Adobe Reader and Acrobat before 9.5, and 10.x before 10.1.2, on Windows and Mac OS X allow attackers to execute arbitrary code or cause a denial of service memory corruption via unspecified vectors, a different vulnerability than CVE-2011-4372 and CVE-2011-4373...
Memory corruption
Adobe Reader and Acrobat before 9.5, and 10.x before 10.1.2, on Windows and Mac OS X allow attackers to execute arbitrary code or cause a denial of service memory corruption via unspecified vectors, a different vulnerability than CVE-2011-4370 and CVE-2011-4373...
CVE-2011-4370
Adobe Reader and Acrobat before 9.5, and 10.x before 10.1.2, on Windows and Mac OS X allow attackers to execute arbitrary code or cause a denial of service memory corruption via unspecified vectors, a different vulnerability than CVE-2011-4372 and CVE-2011-4373...
CVE-2011-4372
Adobe Reader and Acrobat before 9.5, and 10.x before 10.1.2, on Windows and Mac OS X allow attackers to execute arbitrary code or cause a denial of service memory corruption via unspecified vectors, a different vulnerability than CVE-2011-4370 and CVE-2011-4373...
CVE-2011-4370
Adobe Reader/Acrobat vulnerable to memory corruption via JPEG DCT Dequantizer in PDFs, allowing arbitrary code execution or DoS. Affected: Windows and macOS; prior to 9.5, and 10.x before 10.1.2. Root cause: buffer overflow during JPEG resource handling. Exploitation status not detailed in provid...