CVE-2023-20197
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 filesystem image parser for Hierarchical File System Plus (HFS+) 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 incorrect check for completion when a file is decompressed, which may result in a loop condition that could cause the affected software to stop responding. An attacker could exploit this vulnerability by submitting a crafted HFS+ filesystem image to be scanned by ClamAV on an affected device. A successful exploit could allow the attacker to cause the ClamAV scanning process to stop responding, resulting in a DoS condition on the affected software and consuming available system resources. For a description of this vulnerability, see the ClamAV blog .
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 confidenceA denial of service vulnerability exists in ClamAV's Hierarchical File System Plus (HFS+) filesystem image parser. The vulnerability stems from an incorrect check for completion during file decompression, which can cause an infinite loop condition. An unauthenticated attacker can trigger this by submitting a crafted HFS+ filesystem image to be scanned, causing the ClamAV scanning process to hang and consume system resources.
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< 1.22.0< 7.5.13.21586>= 8.0.1.21160, < 8.1.7.21585< 3.8.0= 38CVSS 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 installationRun 'clamd --version' or check your package manager for clamavAffected if ClamAV is installed and no version is returned or version cannot be determined
-
Check Cisco Secure Endpoint versionOn Windows: check 'About' in the Secure Endpoint GUI or check the installed program version. On Mac: use 'System Information' or check /Applications/AmnestyMonitor.appAffected if Version is < 1.22.0, or between 7.5.0 and 7.5.13.21585, or >= 8.0.1.21160 but < 8.1.7.21585 on Windows/Mac agents
-
Check Cisco Secure Endpoint Private Cloud versionCheck the Private Cloud appliance version through the admin console or APIAffected if Version is less than 3.8.0
-
Check Fedora system versionRun 'cat /etc/fedora-release' to confirm Fedora 38Affected if System is Fedora 38 with ClamAV installed from official repositories
-
Verify HFS+ scanning capabilityCheck ClamAV configuration files (clamd.conf, freshclam.conf) for 'hfsplus' signatures or HFS+ related scan optionsAffected if HFS+ scanning is enabled and ClamAV has HFS+ signature databases loaded
You are affected if you are running Cisco Secure Endpoint (Windows/Mac) below version 1.22.0, version 7.5.x below 7.5.13.21586, or versions 8.0.1.21160 through 8.1.7.21585; Cisco Secure Endpoint Private Cloud below 3.8.0; or Fedora 38 with ClamAV, AND you scan HFS+ filesystem images.
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.22.03.8.07.5.13.21586
Update ClamAV to the latest version incorporating the fix for this vulnerability. As an interim measure, avoid scanning untrusted HFS+ filesystem images or disable HFS+ scanning in ClamAV configurations.
Secure Endpoint: 1.22.0+ or 7.5.13.21586+ or 8.1.7.21585+ | Secure Endpoint Private Cloud: 3.8.0+ | Fedora: latest clamav update for Fedora 38
- For Cisco Secure Endpoint (AMP for Endpoints): Upgrade to version 1.22.0 or later, or version 7.5.13.21586 or later, or version 8.1.7.21585 or later depending on your current major version branch
- For Cisco Secure Endpoint Private Cloud: Upgrade to version 3.8.0 or later
- For Fedora 38 systems: Update the clamav package to the version fixed for CVE-2023-20197 (refer to Fedora security advisories for the exact fixed version)
- After upgrading, verify the ClamAV engine version matches the fixed release
- Test that HFS+ filesystem scanning completes successfully without hanging
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.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 $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-20197 — 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-2023-20197 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