CVE-2019-12625
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 · uneditedClamAV versions prior to 0.101.3 are susceptible to a zip bomb vulnerability where an unauthenticated attacker can cause a denial of service condition by sending crafted messages to an affected system.
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 confidenceClamAV versions prior to 0.101.3 are vulnerable to zip bomb attacks where maliciously crafted compressed files decompress to extremely large sizes, causing denial of service by exhausting system resources (memory, CPU, disk space). The vulnerability allows unauthenticated attackers to send crafted messages that trigger this condition.
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< 0.101.3CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.
-
Verify ClamAV is installedRun 'which clamscan' or 'which clamd' to locate the ClamAV binaries, or check your package manager for installed clamav packagesAffected if ClamAV binaries are not found on the system
-
Determine installed ClamAV versionRun 'clamscan --version' or 'clamd --version' to display the exact version number of the installed ClamAV engineAffected if Command fails or returns no version
-
Compare version to affected rangeCompare the installed version number to 0.101.3 - versions less than 0.101.3 (such as 0.101.2, 0.101.1, 0.100.x, 0.99.x) are vulnerableAffected if Installed version is lower than 0.101.3 (e.g., 0.101.2, 0.100.3, 0.100.0, 0.99.5)
-
Check if ClamAV is used to scan archivesReview configuration files (clamd.conf, freshclam.conf) in /etc/clamav/ or review scan policies to confirm ClamAV is configured to scan compressed archivesAffected if ClamAV is actively used to scan archive files (zip, rar, 7z, tar)
You are affected if ClamAV is installed with a version lower than 0.101.3 and is used to scan archive files, as this allows zip bomb attacks to exhaust system resources.
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 data0.101.3
Upgrade to ClamAV version 0.101.3 or later, which includes protection mechanisms against zip bombs by implementing decompression ratio limits and recursion depth controls.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-12625 — 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-2019-12625 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