CVE-2010-1509
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 · uneditedIrfanView before 4.27 does not properly handle an unspecified integer variable during processing of PSD images, which allows remote attackers to cause a denial of service (application crash) or possibly execute arbitrary code via a crafted image file that triggers a heap-based buffer overflow, related to a "sign-extension error."
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 confidenceIrfanView before version 4.27 contains a sign-extension error in PSD (Photoshop Document) image parsing that leads to a heap-based buffer overflow when processing a crafted PSD file. The vulnerability stems from improper handling of an unspecified integer variable, allowing remote attackers to potentially execute arbitrary code or cause a denial of service via a malicious image.
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.25= 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
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/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.
-
Determine IrfanView versionOpen IrfanView and navigate to Help > About, or right-click the IrfanView executable and select Properties to view the version information. If installed via a package manager, use the appropriate command to list installed software version.Affected if The installed version is 4.25 or lower, or matches any of the affected versions listed: 1.70, 1.75, 1.80, 1.85, 1.90, 1.95, 1.97, 1.98, 1.98a, 1.99, or 2.00.
-
Identify PSD file handling capabilityCheck if the IrfanView PSD plugin (psd.dll or similar) is present in the IrfanView plugins directory. This is typically found in a 'Plugins' or 'PlugIns' subfolder within the IrfanView installation directory.Affected if The PSD plugin file exists and is loaded by IrfanView, enabling PSD file parsing.
-
Verify plugin version or dateIf the PSD plugin is present, check its file properties (right-click > Properties > Details) for version or modification date. Compare this against the IrfanView version to confirm it ships with a vulnerable version.Affected if The plugin version corresponds to an IrfanView release before 4.27.
You are affected if IrfanView version is below 4.27 and the PSD plugin is enabled, allowing malicious PSD files to trigger the heap overflow during parsing.
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 dataUpgrade IrfanView to version 4.27 or later. Avoid opening PSD files from untrusted sources until the update is applied.
- Consultation1.0 h
- Implementation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-1509 — 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-2010-1509 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