CVE-2012-0777
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 · uneditedThe JavaScript API in Adobe Reader and Acrobat 9.x before 9.5.1 and 10.x before 10.1.3 on Mac OS X and Linux allows attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors.
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 · moderate confidenceMemory corruption vulnerability in the JavaScript API of Adobe Reader and Acrobat 9.x before 9.5.1 and 10.x before 10.1.3 on Mac OS X and Linux. The flaw allows arbitrary code execution or denial of service via unspecified vectors exploiting the JavaScript API functionality.
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.0, < 9.5.1>= 10.0, < 10.1.3>= 9.0, < 9.5.1>= 10.0, < 10.1.3CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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 if Adobe Reader or Acrobat is installedOn Linux, run 'dpkg -l | grep -i acrobat' or 'rpm -qa | grep -i acrobat' to list installed packages. On Mac OS X, run 'ls /Applications | grep -i adobe' to check Applications folder.Affected if No Adobe Reader or Acrobat package is found (not vulnerable because product not installed)
-
Determine the installed version of Adobe Reader or AcrobatOn Linux, run 'dpkg -l | grep -i acrobat' or 'rpm -qa | grep -i acrobat' to see the version number. On Mac OS X, right-click the Adobe app in Applications, select Get Info, or run 'defaults read /Applications/Adobe\ Reader\ 9.app/Contents/Info CFBundleShortVersionString' (adjust path for your version).Affected if Version is 9.0 to 9.5.0, or 10.0 to 10.1.2 (vulnerable range)
-
Check if JavaScript is enabled in Adobe preferencesOn Linux, inspect the preferences file in ~/.adobe/Acrobat/*/prefs.xml or the global preference file in the Adobe installation directory for the key 'bJSEnable' or similar JavaScript enable setting. On Mac OS X, check ~/Library/Preferences/com.adobe.acrobat.*.plist for 'bJSEnable' key.Affected if JavaScript is enabled (value set to 1, true, or the setting is absent which may default to enabled)
-
Confirm the platform is Mac OS X or LinuxRun 'uname -s' or check the operating system. This CVE only affects Mac OS X and Linux; Windows is not listed as affected.Affected if Running on Windows (not affected by this specific CVE)
You are affected if Adobe Reader or Acrobat version 9.0-9.5.0 or 10.0-10.1.2 is installed on Mac OS X or Linux AND JavaScript is enabled in the application preferences.
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.
From vendor data9.5.110.1.3
Apply vendor updates (Adobe Reader/Acrobat 9.5.1+ or 10.1.3+) or disable JavaScript in Adobe products if updates cannot be deployed promptly.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-0777 — 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-0777 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