CVE-2012-1197
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 · uneditedInteger overflow in the IDE_ACDStd.apl module for ACDSee 14.1 Build 137 allows remote attackers to execute arbitrary code via crafted "image dimension values" in a BMP file, which triggers a heap-based buffer overflow.
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 confidenceACDSee 14.1 Build 137 contains an integer overflow vulnerability in its IDE_ACDStd.apl plugin module. When parsing a BMP file with specially crafted image dimension values, the integer overflow triggers a heap-based buffer overflow, allowing remote attackers to execute arbitrary code.
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= 14.1_build_137CVSS 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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/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 ACDSee versionOpen ACDSee and navigate to Help > About, or check Add/Remove Programs in Windows Control Panel for ACDSee 14.1 Build 137Affected if The installed version matches 14.1_build_137 exactly
-
Locate the IDE_ACDStd.apl plugin fileSearch for IDE_ACDStd.apl in the ACDSee installation directory, typically under C:\Program Files\ACD Systems\ACDSee\14.0\ or similar pathAffected if The IDE_ACDStd.apl file exists in the ACDSee plugins folder
-
Verify BMP file handling is enabledOpen ACDSee, go to Tools > File Associations or Plugins settings, and check if BMP file type is associated with ACDSee for viewingAffected if BMP files are configured to open with ACDSee
-
Check for recent BMP file processing activityReview ACDSee thumbnail cache files or recent file history logs if available, or manually inspect if BMP files can be opened and rendered by ACDSeeAffected if BMP files can be successfully parsed and displayed by ACDSee
You are affected if ACDSee version 14.1_build_137 is installed, the IDE_ACDStd.apl plugin exists, and BMP file processing is enabled in your environment.
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 dataApply the vendor patch when released, or implement defensive controls such as disabling the IDE_ACDStd.apl plugin, restricting BMP file processing to trusted sources, or deploying input validation/anti-exploitation tools.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-1197 — 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-1197 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