# CVE-2023-20197: Denial of service in Cisco Secure Endpoint > An unauthenticated remote attacker can cause a denial of service in ClamAV by submitting a crafted HFS+ filesystem image that triggers an infinite loop during decompression. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 16 Aug 2023 - **Updated:** 2 Aug 2024 - **Also known as:** CLEANSTART-2026-MF37680, DEBIAN-CVE-2023-20197, DLA-3544-1, GHSA-r7mw-p665-4533, OESA-2023-1540, OESA-2023-1557, OESA-2023-1558, OESA-2023-1559, OESA-2023-1560, SUSE-SU-2023:3435-1, SUSE-SU-2023:3456-1, UBUNTU-CVE-2023-20197, USN-6303-1, USN-6303-2, openSUSE-SU-2024:13174-1 ## What is CVE-2023-20197? CVE-2023-20197 is a high-severity denial of service vulnerability in Fedoraproject Fedora, published on 16 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description A 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 . Weakness: CWE-835 (Loop with Unreachable Exit Condition) ## Which versions are affected by CVE-2023-20197? It affects 3 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `clamav` | SUSE:Enterprise Storage 7 | All versions | 0.103.9-150000.3.47.1 | | `clamav` | SUSE:Enterprise Storage 7.1 | All versions | 0.103.9-150000.3.47.1 | | `clamav` | SUSE:Linux Enterprise High Performance Computing 15 SP1-LTSS | All versions | 0.103.9-150000.3.47.1 | | `clamav` | SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | All versions | 0.103.9-150000.3.47.1 | | `clamav` | SUSE:Linux Enterprise High Performance Computing 15 SP3-ESPOS | All versions | 0.103.9-150000.3.47.1 | | `clamav` | SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | All versions | 0.103.9-150000.3.47.1 | | `clamav` | SUSE:Linux Enterprise Module for Basesystem 15 SP4 | All versions | 0.103.9-150000.3.47.1 | | `clamav` | SUSE:Linux Enterprise Module for Basesystem 15 SP5 | All versions | 0.103.9-150000.3.47.1 | | `clamav` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 0.103.9-3.27.1 | | `clamav` | SUSE:Linux Enterprise Server 15 SP1-LTSS | All versions | 0.103.9-150000.3.47.1 | | `clamav` | SUSE:Linux Enterprise Server 15 SP2-LTSS | All versions | 0.103.9-150000.3.47.1 | | `clamav` | SUSE:Linux Enterprise Server 15 SP3-LTSS | All versions | 0.103.9-150000.3.47.1 | | `clamav` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 0.103.9-3.27.1 | | `clamav` | SUSE:Linux Enterprise Server for SAP Applications 15 SP1 | All versions | 0.103.9-150000.3.47.1 | | `clamav` | SUSE:Linux Enterprise Server for SAP Applications 15 SP2 | All versions | 0.103.9-150000.3.47.1 | | `clamav` | SUSE:Linux Enterprise Server for SAP Applications 15 SP3 | All versions | 0.103.9-150000.3.47.1 | | `clamav` | SUSE:Manager Proxy 4.2 | All versions | 0.103.9-150000.3.47.1 | | `clamav` | SUSE:Manager Server 4.2 | All versions | 0.103.9-150000.3.47.1 | | `clamav` | openSUSE:Leap 15.4 | All versions | 0.103.9-150000.3.47.1 | | `clamav` | openSUSE:Leap 15.5 | All versions | 0.103.9-150000.3.47.1 | | `clamav` | openSUSE:Tumbleweed | All versions | 0.103.9-1.1 | Products: Cisco Secure Endpoint, Cisco Secure Endpoint Private Cloud, Fedoraproject Fedora. ## How do I fix CVE-2023-20197? Upgrade to a fixed version. ## Is CVE-2023-20197 being exploited? There is no known exploitation of CVE-2023-20197 in the wild and no public exploit code. ## Other vulnerabilities in Fedoraproject Fedora - [CVE-2023-20032](https://insights.sbomify.com/CVE-2023-20032/): Memory corruption in Cisco Secure Endpoint (critical 9.8) - [CVE-2022-20770](https://insights.sbomify.com/CVE-2022-20770/): ClamAV CHM File Parsing Denial of Service Vulnerability Affecting Cisco Products: April 2022 (high 8.6) - [CVE-2026-20348](https://insights.sbomify.com/CVE-2026-20348/): ClamAV XAR File Format Processing Memory Corruption Vulnerability (high 7.5) - [CVE-2026-20213](https://insights.sbomify.com/CVE-2026-20213/): ClamAV PE File Format Processing Out-of-Bounds Memory Corruption Vulnerability (high 7.5) - [CVE-2026-20214](https://insights.sbomify.com/CVE-2026-20214/): ClamAV FSG File Format Processing Out-of-Bounds Memory Corruption Vulnerability (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-20197 and fix it if it is affected. What it is: CVE-2023-20197 is a high-severity denial of service vulnerability in Fedoraproject Fedora, published on 16 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2023-20197 in the wild and no public exploit code. Affected product: Fedoraproject Fedora. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2023-20197/ (Markdown: https://insights.sbomify.com/CVE-2023-20197/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-20197 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-20197 - OSV: https://osv.dev/vulnerability/CVE-2023-20197 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-20197/ Summaries are generated and may contain mistakes; the official description above is the record.