CVE-2012-0897
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 · uneditedStack-based buffer overflow in the JPEG2000 plugin in IrfanView PlugIns before 4.33 allows remote attackers to execute arbitrary code via a JPEG2000 (JP2) file with a crafted Quantization Default (QCD) marker segment.
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 confidenceStack-based buffer overflow in IrfanView's JPEG2000 plugin (PlugIns before version 4.33) allows remote code execution via a specially crafted JP2 file containing a malformed Quantization Default (QCD) marker segment.
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<= 4.32= 1.70= 1.75= 1.80= 1.85= 1.90= 1.95= 1.97= 1.98= 1.98a= 1.99= 2.00CVSS 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.
-
Locate IrfanView PlugIns directoryFind the PlugIns folder where IrfanView is installed, typically C:\Program Files\IrfanView\PlugIns or C:\Program Files (x86)\IrfanView\PlugIns on 64-bit WindowsAffected if The PlugIns directory exists and contains JPEG2000-related DLL files (jp2.dll, JP2.dll, or similar)
-
Identify JPEG2000 plugin fileIn the PlugIns directory, look for the JPEG2000 plugin file - typically named jp2.dll or JP2.dll - which handles JP2 file parsingAffected if The jp2.dll or JP2.dll file exists in the PlugIns folder
-
Check PlugIns versionRight-click the JPEG2000 plugin file (jp2.dll or JP2.dll), select Properties, then view the Version tab to find the File Version or Product VersionAffected if The plugin version is earlier than 4.33 or the version field shows nothing/is missing (indicating an old unversioned build)
-
Verify main IrfanView versionOpen IrfanView and go to Help > About, or right-click irfanview.exe and check Properties > Details to confirm the installed versionAffected if IrfanView version is 4.32 or below, or matches any of these affected versions: 1.70, 1.75, 1.80, 1.85, 1.90, 1.95, 1.97, 1.98, 1.98a, 1.99, 2.00
A system is affected if the PlugIns directory contains a JPEG2000 plugin (jp2.dll) with version earlier than 4.33, regardless of the main IrfanView application version.
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 dataUpdate IrfanView PlugIns to version 4.33 or later to patch the vulnerable JPEG2000 parsing code that fails to properly validate the QCD marker segment.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-0897 — 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-0897 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