dbcve.org
Secure EndpointApplication · Cisco

CVE-2025-20234

HIGH · 7.5 CVSS v3.1 Published 2025-06-18
Fix available
A fix is available. Upgrade to 1.4.3 / 1.26.1 or later.
See remediation →
84/100
Remediation priority · High
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
A vulnerability in Universal Disk Format (UDF) processing 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 a memory overread during UDF file scanning. An attacker could exploit this vulnerability by submitting a crafted file containing UDF 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 .

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

ClamAV contains a memory overread vulnerability in its Universal Disk Format (UDF) file parsing code. When scanning a specially crafted UDF file, the scanner reads beyond allocated memory boundaries, causing the scanning process to crash and terminate, resulting in denial of service.

MitigationUpdate ClamAV to the version containing the fix for CVE-2025-20234. If immediate patching is not possible, consider disabling UDF scanning or implementing file-type based pre-filtering to reject UDF files at the perimeter until the update can be 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
Secure EndpointApplication
Affected:< 1.26.1< 7.5.21>= 8.0.1.21160, < 8.4.5
Secure Endpoint Private CloudApplication
Affected:< 4.2.2
ClamavApplication
Affected:>= 1.2.0, < 1.4.3

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed ClamAV version
    Run 'clamd --version' or check the package manager for the installed ClamAV version
    Affected if The installed version is >= 1.2.0 and < 1.4.3 for ClamAV, or falls within the affected Cisco Secure Endpoint version ranges
  2. Identify if UDF scanning is enabled
    Inspect the ClamAV configuration files (clamd.conf, freshclam.conf) for 'scanudf' or UDF-related directives
    Affected if UDF scanning is enabled in the configuration
  3. Verify UDF file handling in scanning workflows
    Review scanning logs or policies to determine if UDF files are processed during antivirus scans
    Affected if UDF files are being scanned or processed by the ClamAV engine

A user is affected if they run a vulnerable ClamAV version AND have UDF scanning enabled, and process UDF files through the scanner.

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 1.4.3 / 1.26.1 / 4.2.2 or later
Fixed in 1.4.31.26.14.2.2
Interim mitigation

Update ClamAV to the version containing the fix for CVE-2025-20234. If immediate patching is not possible, consider disabling UDF scanning or implementing file-type based pre-filtering to reject UDF files at the perimeter until the update can be applied.

Recommended fix High confidence

ClamAV: 1.4.3+ | Secure Endpoint: 1.26.1+, 7.5.21+, or 8.4.5+ | Secure Endpoint Private Cloud: 4.2.2+

  1. 1. Identify the specific ClamAV or Cisco Secure Endpoint product and version currently installed
  2. 2. For ClamAV: Upgrade to version 1.4.3 or later
  3. 3. For Secure Endpoint: Upgrade to version 1.26.1 or later (for older release tracks)
  4. 4. For Secure Endpoint: Upgrade to version 7.5.21 or later (for 7.x release track)
  5. 5. For Secure Endpoint: Upgrade to version 8.4.5 or later (for 8.x release track, minimum 8.0.1.21160)
  6. 6. For Secure Endpoint Private Cloud: Upgrade to version 4.2.2 or later
  7. 7. After upgrading, verify the new version is running and re-scan any previously quarantined files if needed
Caveat Ensure compatibility with your deployment environment; check release notes for any behavioral changes in the new version

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

Fix this in Secure Endpoint Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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