dbcve.org
B3dApplication · Irfanview

CVE-2020-13879

CRITICAL · 9.8 CVSS v3.1 Published 2024-01-05
Fix available
A fix is available. Upgrade to 4.56 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
IrfanView B3D PlugIns before version 4.56 has a B3d.dll!+214f heap-based out-of-bounds write.

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 confidence

IrfanView B3D PlugIns before version 4.56 contains a heap-based out-of-bounds write vulnerability in B3d.dll at offset +214f. This memory corruption flaw in the B3D image format parser could allow an attacker to achieve remote code execution by processing a specially crafted B3D file.

MitigationUpgrade IrfanView B3D PlugIns to version 4.56 or later. Avoid opening untrusted B3D files from unknown sources until the patch is applied.

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
B3dApplication
Affected:< 4.56

CVSS 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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the B3d.dll plugin file
    Search for B3d.dll in the IrfanView installation directory, typically under a 'Plugins' or 'PlugIns' subfolder. Common paths include C:\Program Files\IrfanView\PlugIns\B3d.dll or similar.
    Affected if The file exists and is found in the IrfanView plugins directory.
  2. Check the version of B3d.dll
    Right-click on B3d.dll, select Properties, then go to the Details tab to view the File Version. Alternatively, use a tool like exiftool or a PowerShell command like (Get-Item 'C:\Path\To\B3d.dll').VersionInfo to retrieve version metadata.
    Affected if The displayed File Version is lower than 4.56 (e.g., 4.55, 4.54, etc.).
  3. Identify the plugin version from file metadata
    Inspect the Product Version or Version Info embedded in B3d.dll using a PE viewer, or check the IrfanView plugins readme/changelog that ships with the installation for the B3D plugin version number.
    Affected if The B3D plugin version listed in the metadata or documentation is less than 4.56.
  4. Confirm B3D format support is available
    Open IrfanView and attempt to open a B3D file, or check the 'Plugins' menu in IrfanView for B3D-related entries. The vulnerability only applies when the B3D parser is active.
    Affected if IrfanView can load or recognizes B3D files, indicating the B3D plugin is enabled and the vulnerable parser code is present.

A user is affected if B3d.dll exists with a version lower than 4.56 and the B3D plugin is enabled, allowing processing of B3D image files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 4.56 or later
Fixed in 4.56
Interim mitigation

Upgrade IrfanView B3D PlugIns to version 4.56 or later. Avoid opening untrusted B3D files from unknown sources until the patch is applied.

Recommended fix Moderate confidence

B3D PlugIn version 4.56

  1. Navigate to the official IrfanView plugin download page or trusted mirror
  2. Locate the B3D plugin (B3d.dll) download section
  3. Download version 4.56 or later of the B3D plugin
  4. Replace the existing B3d.dll file in the IrfanView plugins directory with the new version
  5. Verify the file version by right-clicking the new B3d.dll, selecting Properties, and checking the Details tab for version 4.56 or higher
  6. Restart IrfanView if it was running during the update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in B3d Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-13879 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-13879 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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