Secure EndpointApplication · Cisco
CVE-2025-20128
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 vulnerability in the Object Linking and Embedding 2 (OLE2) decryption routine of ClamAV could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition on an affected device. This vulnerability is due to an integer underflow in a bounds check that allows for a heap buffer overflow read. An attacker could exploit this vulnerability by submitting a crafted file containing OLE2 content to be scanned by ClamAV on an affected device. A successful exploit could allow the attacker to terminate the ClamAV scanning process, resulting in a DoS condition on the affected software. For a description of this vulnerability, see the . Cisco has released software updates that address this vulnerability. There are no workarounds that address this vulnerability.
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 contains an integer underflow vulnerability in the OLE2 decryption routine's bounds checking logic, which allows a heap buffer overflow read. An unauthenticated remote attacker can trigger this by submitting a crafted OLE2 file to be scanned, causing the ClamAV scanning process to crash (DoS).
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
Secure EndpointApplication
< 1.24.4< 1.25.1< 7.5.20>= 8.0.1.21160, < 8.4.3
Secure Endpoint Private CloudApplication
< 4.2.0>= 1.0.0, < 1.0.8>= 1.1.0, < 1.4.2CVSS 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.
-
Identify ClamAV installation and versionRun 'clamd --version' or 'clamscan --version' to determine the installed ClamAV version and build informationAffected if The installed version falls within >= 1.0.0 and < 1.0.8, or >= 1.1.0 and < 1.4.2 for open-source ClamAV; or within the affected Cisco Secure Endpoint version ranges listed in the CVE
-
Confirm OLE2 file scanning capability is presentVerify the ClamAV engine has OLE2 support compiled in by checking 'clamscan --debug 2>&1 | grep -i ole' or examining the engine capabilities outputAffected if OLE2 support is present in the installation (the vulnerability exists in the OLE2 decryption code path)
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.
dbcve · scoped1.0.81.4.21.24.4
Apply the Cisco software update for ClamAV that addresses this vulnerability. No workarounds are available.
ClamAV: 1.0.8+ or 1.4.2+ | Secure Endpoint: 1.24.4+, 1.25.1+, 7.5.20+, or 8.4.3+ | Secure Endpoint Private Cloud: 4.2.0+
- 1. Identify current ClamAV or Secure Endpoint version using 'clamd --version' or checking the product UI
- 2. For ClamAV: if running version >= 1.0.0 and < 1.0.8, upgrade to 1.0.8 or later
- 3. For ClamAV: if running version >= 1.1.0 and < 1.4.2, upgrade to 1.4.2 or later
- 4. For Secure Endpoint: upgrade to version 1.24.4, 1.25.1, 7.5.20, or 8.4.3 (depending on current major version)
- 5. For Secure Endpoint Private Cloud: upgrade to version 4.2.0 or later
- 6. After upgrade, verify the new version is running with 'clamd --version'
- 7. Test with a sample OLE2 file to confirm scanning completes without crash
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Secure Endpoint
Scoped from the published advisory
- Consultation3.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20128 — 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-2025-20128 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