CVE-2012-3585
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 · uneditedHeap-based buffer overflow in jpeg_ls.dll in the Jpeg_LS (aka JLS) plugin in the formats plugins in IrfanView PlugIns before 4.34 allows remote attackers to execute arbitrary code via a crafted JLS file.
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 confidenceHeap-based buffer overflow in jpeg_ls.dll (Jpeg_LS/JLS plugin) in IrfanView PlugIns versions before 4.34 allows remote code execution when processing a specially crafted JLS image file. The vulnerability stems from insufficient bounds checking when parsing JLS file headers, causing overflow of heap-allocated memory.
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.33CVSS 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.
-
Locate IrfanView Plugins installation directoryLook for the IrfanView PlugIns folder, typically found in paths like C:\Program Files\IrfanView\PlugIns or C:\Program Files (x86)\IrfanView\PlugIns on Windows systemsAffected if The PlugIns folder does not exist - IrfanView Plugins are not installed
-
Identify the jpeg_ls.dll plugin fileCheck if jpeg_ls.dll or JLS.dll exists in the PlugIns folder - this is the Jpeg_LS/JLS plugin that contains the vulnerabilityAffected if The jpeg_ls.dll file exists in the PlugIns directory, indicating the vulnerable component is present
-
Determine IrfanView Plugins versionCheck the version of the installed IrfanView Plugins - look for version info in the file properties of the PlugIns folder or check the IrfanView website/download for the installed version numberAffected if Installed version is 4.33 or earlier (versions before 4.34 are affected)
-
Verify plugin is enabled in IrfanViewOpen IrfanView, go to menu: Options > Properties/Settings > PlugIns - confirm the JLS plugin is loaded and not disabled or removedAffected if The JLS/Jpeg_LS plugin is enabled and available for processing JLS image files
A user is affected if IrfanView Plugins version 4.33 or earlier is installed with the jpeg_ls.dll plugin present and enabled, allowing processing of JLS image files that could trigger the heap overflow.
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 · scopedUpdate IrfanView PlugIns to version 4.34 or later. Until patched, exercise caution with untrusted JLS files and consider disabling the JLS plugin or using application whitelisting.
IrfanView PlugIns 4.34 or later
- Download IrfanView PlugIns version 4.34 or later from the official IrfanView website (irfanview.com)
- Extract the downloaded plugins package
- Replace the existing jpeg_ls.dll in your IrfanView PlugIns directory with the new version from the updated package
- Restart IrfanView if it was running
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-3585 — 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-3585 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