# CVE-2024-20696: Windows libarchive Remote Code Execution Vulnerability > An attacker can execute arbitrary code on Windows systems by exploiting a heap-based buffer overflow in the libarchive component. - **Severity:** High 7.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 9 Jan 2024 - **Updated:** 3 Nov 2025 - **Also known as:** ALPINE-CVE-2024-20696, CLSA-2026-1775647149, CLSA-2026-1775689506, DEBIAN-CVE-2024-20696, DSA-5806-1, GHSA-g5xc-jv8h-2232, MGASA-2024-0363, OESA-2024-1715, SUSE-SU-2024:2081-1, SUSE-SU-2024:2082-1, SUSE-SU-2024:2171-1, SUSE-SU-2024:2171-2, UBUNTU-CVE-2024-20696, USN-7087-1, openSUSE-SU-2024:14378-1 ## What is CVE-2024-20696? CVE-2024-20696 is a high-severity memory corruption vulnerability in Microsoft Windows 10 1809, published on 9 Jan 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. ### Official description Windows libarchive Remote Code Execution Vulnerability Weakness: CWE-122 (Heap-based Buffer Overflow) ## Which versions are affected by CVE-2024-20696? It affects 9 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `libarchive` | SUSE:Enterprise Storage 7.1 | All versions | 3.4.2-150200.4.18.1 | | `libarchive` | SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | All versions | 3.4.2-150200.4.18.1 | | `libarchive` | SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | All versions | 3.4.2-150200.4.18.1 | | `libarchive` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 3.5.1-150400.3.15.1 | | `libarchive` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 3.5.1-150400.3.15.1 | | `libarchive` | SUSE:Linux Enterprise Micro 5.3 | All versions | 3.5.1-150400.3.15.1 | | `libarchive` | SUSE:Linux Enterprise Micro 5.4 | All versions | 3.5.1-150400.3.15.1 | | `libarchive` | SUSE:Linux Enterprise Micro 5.5 | All versions | 3.5.1-150400.3.15.1 | | `libarchive` | SUSE:Linux Enterprise Micro 5.5 | All versions | 3.5.1-150400.3.15.1 | | `libarchive` | SUSE:Linux Enterprise Module for Basesystem 15 SP5 | All versions | 3.5.1-150400.3.15.1 | | `libarchive` | SUSE:Linux Enterprise Module for Development Tools 15 SP5 | All versions | 3.5.1-150400.3.15.1 | | `libarchive` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 3.3.3-32.11.1 | | `libarchive` | SUSE:Linux Enterprise Server 15 SP2-LTSS | All versions | 3.4.2-150200.4.18.1 | | `libarchive` | SUSE:Linux Enterprise Server 15 SP3-LTSS | All versions | 3.4.2-150200.4.18.1 | | `libarchive` | SUSE:Linux Enterprise Server 15 SP4-LTSS | All versions | 3.5.1-150400.3.15.1 | | `libarchive` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 3.3.3-32.11.1 | | `libarchive` | SUSE:Linux Enterprise Server for SAP Applications 15 SP2 | All versions | 3.4.2-150200.4.18.1 | | `libarchive` | SUSE:Linux Enterprise Server for SAP Applications 15 SP3 | All versions | 3.4.2-150200.4.18.1 | | `libarchive` | SUSE:Linux Enterprise Server for SAP Applications 15 SP4 | All versions | 3.5.1-150400.3.15.1 | | `libarchive` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 3.3.3-32.11.1 | | `libarchive` | SUSE:Manager Proxy 4.3 | All versions | 3.5.1-150400.3.15.1 | | `libarchive` | SUSE:Manager Server 4.3 | All versions | 3.5.1-150400.3.15.1 | | `libarchive` | openSUSE:Leap 15.5 | All versions | 3.5.1-150400.3.15.1 | | `libarchive` | openSUSE:Leap Micro 5.3 | All versions | 3.5.1-150400.3.15.1 | | `libarchive` | openSUSE:Leap Micro 5.4 | All versions | 3.5.1-150400.3.15.1 | | `libarchive` | openSUSE:Tumbleweed | All versions | 3.7.6-1.1 | Products: Microsoft Windows 10 1809, Microsoft Windows 10 21h2, Microsoft Windows 10 22h2, Microsoft Windows 11 21h2, Microsoft Windows 11 22h2, Microsoft Windows 11 23h2, Microsoft Windows Server 2019, Microsoft Windows Server 2022, Microsoft Windows Server 2022 23h2. ## How do I fix CVE-2024-20696? Apply the vendor's patch. ## Is CVE-2024-20696 being exploited? There is no known exploitation of CVE-2024-20696 in the wild and no public exploit code. Public exploit code: - https://github.com/clearbluejar/CVE-2024-20696 (github_poc): https://github.com/clearbluejar/CVE-2024-20696 ## Other vulnerabilities in Microsoft Windows 10 1809 - [CVE-2024-29988](https://insights.sbomify.com/CVE-2024-29988/): Microsoft SmartScreen Prompt Security Feature Bypass (high 8.8, exploited in the wild) - [CVE-2024-21412](https://insights.sbomify.com/CVE-2024-21412/): Microsoft Windows Internet Shortcut Files Security Feature Bypass (high 8.1, exploited in the wild) - [CVE-2025-62221](https://insights.sbomify.com/CVE-2025-62221/): Microsoft Windows Use After Free (high 7.8, exploited in the wild) - [CVE-2025-30400](https://insights.sbomify.com/CVE-2025-30400/): Microsoft Windows DWM Core Library Use-After-Free (high 7.8, exploited in the wild) - [CVE-2024-21338](https://insights.sbomify.com/CVE-2024-21338/): Microsoft Windows Kernel Exposed IOCTL with Insufficient Access Control (high 7.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-20696 and fix it if it is affected. What it is: CVE-2024-20696 is a high-severity memory corruption vulnerability in Microsoft Windows 10 1809, published on 9 Jan 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2024-20696 in the wild and no public exploit code. Affected product: Microsoft Windows 10 1809. 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-2024-20696/ (Markdown: https://insights.sbomify.com/CVE-2024-20696/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-20696 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-20696 - OSV: https://osv.dev/vulnerability/CVE-2024-20696 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-20696/ Summaries are generated and may contain mistakes; the official description above is the record.