dbcve.org
XnviewApplication

CVE-2013-3941

CRITICAL · 9.8 CVSS v3.1 Published 2020-01-02
Fix available
A fix is available. Upgrade to 2.13 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
Xjp2.dll in XnView before 2.13 allows remote attackers to execute arbitrary code via (1) the Csiz parameter in a SIZ marker, which triggers an incorrect memory allocation, or (2) the lqcd field in a QCD marker in a crafted JPEG2000 file, which leads to 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 confidence

XnView's Xjp2.dll JPEG2000 parsing library contains two critical memory corruption vulnerabilities in versions before 2.13. The first flaw involves incorrect memory allocation triggered by the Csiz parameter in SIZ markers, while the second involves a heap-based buffer overflow from the lqcd field in QCD markers. Both can be triggered by processing specially crafted JPEG2000 files, allowing remote code execution.

MitigationUpdate XnView to version 2.13 or later to patch the vulnerable Xjp2.dll component; avoid opening untrusted JPEG2000 files until the update 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
XnviewApplication
Affected:< 2.13

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. Check XnView installed version
    Open XnView, go to Help > About, or find XnView.exe in the installation directory and check its version properties. Alternatively, check the version listed in Add/Remove Programs (Windows) or the installed package (Linux).
    Affected if version is below 2.13
  2. Locate and verify Xjp2.dll version
    Search for Xjp2.dll in the XnView installation folder (commonly in C:\Program Files\XnView or /opt/xnview). Right-click the file, select Properties, and check the File Version field.
    Affected if Xjp2.dll exists with a version below 2.13 or if the file exists but has no version info while XnView version is below 2.13
  3. Confirm JPEG2000 file handling is available
    Attempt to open a JPEG2000 (.jp2, .j2k) file in XnView, or check File > Properties for supported formats. Verify the Xjp2.dll library is being loaded during JPEG2000 processing.
    Affected if XnView can process JPEG2000 files and the vulnerable Xjp2.dll component is loaded
  4. Compare against affected version range
    Review all gathered version information against the known affected range: XnView versions prior to 2.13 contain the vulnerable Xjp2.dll.
    Affected if Installed XnView and Xjp2.dll are both below version 2.13 and JPEG2000 processing is functional

The environment is affected if XnView version is below 2.13, the Xjp2.dll component exists in the installation, and the application can process JPEG2000 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 2.13 or later
Fixed in 2.13
Interim mitigation

Update XnView to version 2.13 or later to patch the vulnerable Xjp2.dll component; avoid opening untrusted JPEG2000 files until the update is applied.

Recommended fix High confidence

XnView 2.13

  1. Navigate to the official XnView website or a trusted download source
  2. Download XnView version 2.13 or later
  3. Verify the file integrity using available checksums if provided
  4. Uninstall the current version of XnView if already installed
  5. Install the downloaded XnView 2.13 or newer version
  6. Verify the installation was successful by checking the installed version

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

Fix this in Xnview Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-3941 — 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-2013-3941 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