dbcve.org
Out-of-bounds ReadWeakness · CWE-125

CVE-2025-53367

HIGH · 8.4 CVSS v4.0 Published 2025-07-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
No privileges

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
DjVuLibre is a GPL implementation of DjVu, a web-centric format for distributing documents and images. Prior to version 3.5.29, the MMRDecoder::scanruns method is affected by an OOB-write vulnerability, because it does not check that the xr pointer stays within the bounds of the allocated buffer. This can lead to writes beyond the allocated memory, resulting in a heap corruption condition. An out-of-bounds read with pr is also possible for the same reason. This issue has been patched in version 3.5.29.

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

The MMRDecoder::scanruns method in DjVuLibre versions prior to 3.5.29 contains an out-of-bounds write vulnerability due to insufficient bounds checking on the xr pointer, allowing writes beyond the allocated buffer and causing heap corruption. A related OOB-read vulnerability exists with the pr pointer for the same reason.

MitigationUpgrade DjVuLibre to version 3.5.29 or later to patch the vulnerability. If immediate upgrade is not feasible, implement input validation on DjVu files before processing and consider isolating the DjVu parsing component to limit blast radius.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Local
Complexity
Low
Privileges
None
Authentication
X
User interaction
A
Scope
X

CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Identify DjVuLibre installation
    Run 'djvutxt --version' or check package manager (dpkg -l | grep djvulibre, rpm -qa | grep djvulibre, or locate libdjvulibre)
    Affected if DjVuLibre is installed and version is below 3.5.29
  2. Confirm installed version number
    Execute 'ddjvu -version' or check the shared library version with 'ldconfig -p | grep djvu' and inspect the file version info
    Affected if Version returned is less than 3.5.29 or no version is displayed (implies older unversioned build)
  3. Determine if MMRDecoder is in use
    Monitor process execution of applications that parse DjVu files (ddjvu, djvutxt, djvups, or any application linked against libdjvulibre)
    Affected if DjVu file decoding functionality is being invoked with the MMRDecoder component
  4. Check for DjVu file processing
    Inspect any custom code or scripts that process .djvu files, or audit running services that accept DjVu input
    Affected if The environment processes untrusted DjVu files using DjVuLibre versions prior to 3.5.29
  5. Identify dependent applications
    Run 'ldd <application>' on any binaries that may handle DjVu format, or check for libdjvulibre.so usage with 'find /usr -name "*djvu*" -type f'
    Affected if Applications are linked against libdjvulibre.so from a version prior to 3.5.29

You are affected if DjVuLibre version 3.5.29 or later is not installed and your environment processes DjVu files using the MMRDecoder component.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade DjVuLibre to version 3.5.29 or later to patch the vulnerability. If immediate upgrade is not feasible, implement input validation on DjVu files before processing and consider isolating the DjVu parsing component to limit blast radius.

Recommended fix High confidence

3.5.29

  1. Check current DjVuLibre version installed (e.g., `djvulibre --version` or `djvm --version`)
  2. Download DjVuLibre version 3.5.29 from the official source (e.g., SourceForge or DjVuLibre official site)
  3. Extract the downloaded archive
  4. Navigate to the extracted directory
  5. Run `./configure` to prepare the build
  6. Run `make` to compile the software
  7. Run `make install` with appropriate privileges to install the upgraded version
  8. Verify the installed version is 3.5.29 or later

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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