Debian LinuxOperating system · Debian
CVE-2021-32492
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 · uneditedA flaw was found in djvulibre-3.5.28 and earlier. An out of bounds read in function DJVU::DataPool::has_data() via crafted djvu file may lead to application crash and other consequences.
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 confidenceAn out-of-bounds read vulnerability exists in DJVU::DataPool::has_data() function in djvulibre versions 3.5.28 and earlier. A specially crafted DJVU file can trigger the vulnerability, causing the application to read memory outside allocated bounds, potentially leading to application crash or information disclosure.
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
Debian LinuxOperating system
= 10.0= 11.0<= 3.5.28CVSS 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
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Check if Djvulibre is installedOn Debian-based systems, run: dpkg -l | grep -i djvulibre or check for binaries (djvu, ddjvu, djvutoxml) with which djvu. On other systems, look for libdjvulibre library files in /usr/lib/ or search for djvulibre-related packages.Affected if Djvulibre or its libraries are present on the system
-
Determine the installed Djvulibre versionRun ddjvu --version or djvu --version to get the version number. On Debian, also run: apt-cache policy djvulibre to see the installed version.Affected if The version displayed is 3.5.28 or earlier, or the package version matches Debian 10.0 or 11.0 which ship the vulnerable version
-
Identify applications using DjvulibreReview installed software that handles DJVU files: document converters, image viewers, PDF tools, or content management systems. Check which packages depend on libdjvulibre with: apt-cache rdepends libdjvulibre.Affected if Any application that processes DJVU files is installed and uses the Djvulibre library
-
Assess the file processing attack surfaceDetermine if the system processes DJVU files from untrusted sources, such as file uploads, email attachments, web content, or networked document workflows. Review any services that handle DJVU format.Affected if DJVU files from untrusted or external sources are processed by any application linked against Djvulibre
The environment is affected if Djvulibre version 3.5.28 or earlier is installed and any application uses it to process DJVU files, particularly from untrusted sources.
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 to djvulibre version 3.5.29 or later. Until patches are available, exercise caution when opening DJVU files from untrusted sources.
Fix this in Debian Linux
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing8.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,472.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-32492 — 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-2021-32492 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