CVE-2012-5680
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 · uneditedBuffer overflow in Adobe Photoshop Camera Raw before 7.3 allows attackers to execute arbitrary code 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 confidenceBuffer overflow vulnerability in Adobe Photoshop Camera Raw plugin affecting versions prior to 7.3. The flaw allows remote attackers to execute arbitrary code via unspecified attack vectors, likely through malicious image files processed by the Camera Raw plugin.
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<= 7.2= 2.1= 2.2= 2.3= 2.4= 3.1= 3.2= 3.3= 3.4= 3.5= 3.6= 3.7CVSS 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 if Adobe Camera Raw plugin is installedCheck for the Camera Raw plugin files on the system. Common locations include Photoshop plug-in folders (e.g., 'Plug-Ins' folder within the Photoshop installation directory). Look for files named 'Camera Raw.8bi' or similar Camera Raw plugin files.Affected if Camera Raw plugin files are found on the system
-
Determine the installed Camera Raw versionRight-click the Camera Raw plugin file and select Properties, then view the Details or Version tab to find the file version. Alternatively, open Adobe Photoshop, go to Help > About Plug-In > Camera Raw to display the version number.Affected if The displayed version is 7.2 or earlier, or matches any of these specific versions: 2.1, 2.2, 2.3, 2.4, 3.1, 3.2, 3.3, 3.4, 3.5, 3.6, or 3.7
-
Verify the Camera Raw functionality is in useConfirm that the system processes image files (particularly RAW formats like CR2, NEF, DNG, ARW) that trigger the Camera Raw plugin. This can be observed when opening such files in Adobe Photoshop or Adobe Lightroom.Affected if The Camera Raw plugin processes image files and the version is within the affected range
A user is affected if the Camera Raw plugin is installed with a version of 7.2 or earlier, or any of the specific affected versions 2.1 through 3.7, and the plugin is actively used to process image files.
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 Photoshop Camera Raw to version 7.3 or later to remediate the vulnerability.
Adobe Camera Raw 7.3 or later
- Upgrade Adobe Photoshop Camera Raw to version 7.3 or later
- Verify the installed Camera Raw version through Photoshop's Help > About Plug-ins > Camera Raw
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-5680 — 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-5680 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