Secure EndpointApplication · Cisco
CVE-2023-20052
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 · uneditedOn Feb 15, 2023, the following vulnerability in the ClamAV scanning library was disclosed: A vulnerability in the DMG file parser of ClamAV versions 1.0.0 and earlier, 0.105.1 and earlier, and 0.103.7 and earlier could allow an unauthenticated, remote attacker to access sensitive information on an affected device. This vulnerability is due to enabling XML entity substitution that may result in XML external entity injection. An attacker could exploit this vulnerability by submitting a crafted DMG file to be scanned by ClamAV on an affected device. A successful exploit could allow the attacker to leak bytes from any file that may be read by the ClamAV scanning process.
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 confidenceThis is an XML External Entity (XXE) injection vulnerability in ClamAV's DMG file parser. The parser enables XML entity substitution, allowing crafted DMG files to reference external entities. By submitting a malicious DMG file, an attacker can leak bytes from any file readable by the ClamAV scanning process, enabling 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
Secure EndpointApplication
< 1.20.2< 1.21.1< 7.5.9>= 8.0.1.21160, < 8.1.5
Secure Endpoint Private CloudApplication
< 3.6.0<= 0.103.7>= 0.104.0, <= 0.105.1= 1.0.0>= 3.0.0, < 3.7.35>= 3.8.0, < 3.11.23>= 4.3.0, < 4.3.17>= 4.4.0, < 4.6.4CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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 installed ClamAV versionRun `clamscan --version` or `clamd --version` to retrieve the ClamAV engine versionAffected if The version is <= 0.103.7, >= 0.104.0 and <= 0.105.1, or exactly 1.0.0
-
Check if DMG file scanning is usedReview scanning configurations, file type signatures, or look for DMG in the scan scope or recent scan logsAffected if DMG files are being scanned by ClamAV (the DMG parser processes these files and is vulnerable)
-
Check Cisco Secure Endpoint version (if applicable)Inspect the installed package version or use the endpoint agent management console to view the agent versionAffected if Version is < 1.20.2, < 1.21.1, < 7.5.9, >= 8.0.1.21160 but < 8.1.5, or any version < 8.0.1.21160 in the 8.x branch
-
Check Cisco Secure Endpoint Private Cloud version (if applicable)View the Private Cloud appliance version in the management interface or system informationAffected if Version is < 3.6.0
-
Check Stormshield Network Security version (if applicable)Inspect the SNS firmware version via the administration interface or `fwadmin --version`Affected if Version is >= 3.0.0 and < 3.7.35, >= 3.8.0 and < 3.11.23, >= 4.3.0 and < 4.3.17, or >= 4.4.0 and < 4.6.4
You are affected if you are running any affected version of ClamAV, Cisco Secure Endpoint, or Stormshield Network Security AND you scan DMG files with the vulnerable DMG parser enabled.
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.20.21.21.13.6.0
Update ClamAV to version 1.0.1 or later, 0.105.2 or later, or 0.103.8 or later to patch the vulnerable DMG parser.
ClamAV 1.0.1+ (or 0.105.2+ / 0.103.8+); Cisco Secure Endpoint 8.1.5+; Stormshield 4.6.4+
- 1. Identify the specific ClamAV version currently installed by running 'clamd --version' or checking your package manager
- 2. For ClamAV standalone: upgrade to version 1.0.1 or later (or 0.105.2+ / 0.103.8+ if staying on older major branches)
- 3. For Cisco Secure Endpoint: upgrade to version 1.20.2 or later, 1.21.1 or later, 7.5.9 or later, or 8.1.5 or later depending on your current branch
- 4. For Cisco Secure Endpoint Private Cloud: upgrade to version 3.6.0 or later
- 5. For Stormshield Network Security: upgrade to version 3.7.35 or later, 3.11.23 or later, 4.3.17 or later, or 4.6.4 or later depending on your current branch
- 6. After upgrade, verify the new version is running with 'clamd --version'
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-2023-20052 — 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-20052 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