CVE-2012-4157
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-4158, CVE-2012-4159, 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 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.
-
Verify Adobe Reader installation on WindowsOpen Control Panel, go to Programs and Features (or Add or Remove Programs), and look for 'Adobe Reader' in the list of installed software. Note the version number displayed.Affected if Adobe Reader is installed and the version listed is 9.0 through 9.4.x (any version below 9.5.2)
-
Verify Adobe Acrobat installation on WindowsOpen Control Panel, go to Programs and Features, and look for 'Adobe Acrobat' in the list of installed software. Note the version number displayed.Affected if Adobe Acrobat is installed and the version listed is 9.0 through 9.3.4 (any version below 9.5.2)
-
Find exact version via executable properties on WindowsNavigate to the Adobe installation directory (typically C:\Program Files\Adobe\Reader X.X\Reader or C:\Program Files\Adobe\Acrobat X.X\Acrobat), right-click the executable file (AcroRd32.exe or AcroTray.exe for Reader, AcroBat.exe or Acrobat.exe for Acrobat), select Properties, and check the Details tab for the Product Version.Affected if The Product Version shown is below 9.5.2 for 9.x versions, or the installed version is any 10.x version below 10.1.4
-
Check version on Mac OS XOpen Finder, navigate to Applications folder, locate Adobe Reader or Adobe Acrobat, right-click the application, select Get Info, and check the Version number under the General information section.Affected if The version shown is 9.x below 9.5.2 or 10.x below 10.1.4
Your environment is affected if Adobe Reader or Adobe Acrobat is installed with any version from 9.0 through 9.3.4 (for Acrobat) or 9.0 through 9.4 (for Reader), or any 10.x version below 10.1.4, on Windows or Mac OS X.
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 · scopedUpgrade Adobe Reader and Acrobat to version 9.5.2 or later (for 9.x) or 10.1.4 or later (for 10.x) to remediate this vulnerability.
Adobe Reader/Acrobat 9.5.2 or later (or 10.1.4 or later for version 10.x)
- 1. Verify the current Adobe Reader or Acrobat version by opening the application, selecting 'Help' > 'About Adobe Reader/Acrobat'
- 2. Navigate to the Adobe Security Bulletin APSB12-16 at http://www.adobe.com/support/security/bulletins/apsb12-16.html
- 3. Download the appropriate update for your version: Adobe Reader 9.5.2 or later, or Adobe Acrobat 9.5.2 or later (or 10.1.4 or later if using version 10.x)
- 4. Close all Adobe Reader/Acrobat instances
- 5. Run the installer and follow the prompts to complete the installation
- 6. Verify the update was successful by checking the version again
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-4157 — 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-4157 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