CVE-2012-4159
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAdobe Reader and Acrobat 9.x before 9.5.2 and 10.x before 10.1.4 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-2012-2051, CVE-2012-4147, CVE-2012-4148, CVE-2012-4149, CVE-2012-4150, CVE-2012-4151, CVE-2012-4152, CVE-2012-4153, CVE-2012-4154, CVE-2012-4155, CVE-2012-4156, CVE-2012-4157, CVE-2012-4158, and CVE-2012-4160.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceMemory corruption vulnerability in Adobe Reader and Acrobat 9.x before 9.5.2 and 10.x before 10.1.4 on Windows and Mac OS X allows remote attackers to execute arbitrary code or cause a denial of service via unspecified vectors.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 9= 9.0= 9.1= 9.1.1= 9.1.2= 9.1.3= 9.2= 9.3= 9.3.1= 9.3.2= 9.3.3= 9.3.4= 9.0= 9.1= 9.1.1= 9.1.2= 9.1.3= 9.2= 9.3= 9.3.1= 9.3.2= 9.3.3= 9.3.4= 9.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Adobe productCheck for Adobe Acrobat or Adobe Acrobat Reader installation. On Windows, open Programs and Features or check C:\Program Files\Adobe\ for Acrobat/Reader folders. On Mac, check /Applications for Adobe Acrobat or Adobe Reader.Affected if Neither Adobe Acrobat nor Adobe Acrobat Reader is installed on the system.
-
Determine installed version numberOn Windows, right-click the Adobe executable (Acrobat.exe or AcroRd32.exe), select Properties, and check the Details tab for Product Version. On Mac, right-click the application in /Applications, select Get Info, and check the Version field.Affected if Unable to determine the installed version from the executable properties.
-
Compare against affected versionsCompare your installed version to the following vulnerable ranges: Adobe Acrobat versions 9 through 9.3.4 (all 9.x versions before 9.5.2) and Adobe Acrobat Reader versions 9.0 through 9.4 (all 9.x versions before 9.5.2). For 10.x line, versions before 10.1.4 are also affected.Affected if Installed version matches any version in the 9.x range before 9.5.2 or any 10.x version before 10.1.4.
-
Verify product type and editionConfirm whether the installation is Adobe Acrobat (full) or Adobe Acrobat Reader (free version). Both product lines share the same version numbering but are tracked separately in the affected products list.Affected if The installed product is Adobe Acrobat or Adobe Acrobat Reader but the specific edition cannot be confirmed.
Your environment is affected if Adobe Acrobat or Adobe Acrobat Reader version 9.x is earlier than 9.5.2, or version 10.x is earlier than 10.1.4.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpdate Adobe Reader and Acrobat to version 9.5.2 or later (for 9.x) or 10.1.4 or later (for 10.x) to patch the vulnerability.
Adobe Acrobat 9.5.2 (for 9.x) or 10.1.4 (for 10.x); Adobe Reader 9.5.2 (for 9.x) or 10.1.4 (for 10.x)
- Check the currently installed Adobe Acrobat or Adobe Reader version by opening the application and navigating to Help > About Adobe Acrobat Reader or About Adobe Acrobat
- Navigate to the Adobe Security Bulletin APSB12-16 at http://www.adobe.com/support/security/bulletins/apsb12-16.html
- Download the appropriate security update from the Adobe download page: For Adobe Acrobat 9.x, download version 9.5.2; For Adobe Acrobat 10.x, download version 10.1.4; For Adobe Reader 9.x, download version 9.5.2; For Adobe Reader 10.x, download version 10.1.4
- Close all Adobe applications and any web browsers with PDF viewing capabilities
- Run the downloaded installer to apply the security update
- Restart the computer after installation completes
- Verify the update was successful by checking the version again in Help > About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-4159 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2012-4159 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data