CVE-2024-20697 | Windows libarchive Remote Code Execution Vulnerability

Windows libarchive Remote Code Execution Vulnerability

Published: 2024-01-09 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-20697 is rated Moderate Risk (64.9/100): CVSS High severity, with high exploitation likelihood (EPSS 49.43%, 98th percentile). EPSS ranks this CVE among the most likely to be exploited in the near term. EPSS rose +1.51% over the last day, indicating growing attacker interest. High exploitation likelihood—assess exposure and prioritize remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2024-20697

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-11-21 47.91% 49.43% +1.51%
2 2025-11-18 49.43% 47.91% -1.51%
3 2025-08-04 — 49.43% —

Full EPSS history (26 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-20697

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.3 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.3 5.9 [email protected]

Weakness enumeration for CVE-2024-20697

OS Trackers for CVE-2024-20697

vendor priority summary link
redhat medium — https://access.redhat.com/security/cve/CVE-2024-20697
suse high CVE-2024-20697 severity important: SUSE including 251 source package names (0.23.1-12.3:libarchive13-3.7.2-150600.3.9.1, 0.3.2-1.2:libarchive13-3.7.2-150600.3.9.1, …), 425 product×package rows across 88 product lines (Container bci/spack, Container containers/lmcache-vllm-openai, … (88 product lines)): Known Affected 231, Known Not Affected 145, Fixed 49. https://www.suse.com/security/cve/CVE-2024-20697/

Affected software / configurations for CVE-2024-20697

Vendor Product Version Raw CPE
microsoft windows_11_22h2 < 10.0.22621.3007 cpe:2.3:o:microsoft:windows_11_22h2:*:*:*:*:*:*:arm64:*
microsoft windows_11_22h2 < 10.0.22621.3007 cpe:2.3:o:microsoft:windows_11_22h2:*:*:*:*:*:*:x64:*
microsoft windows_11_23h2 < 10.0.22631.3007 cpe:2.3:o:microsoft:windows_11_23h2:*:*:*:*:*:*:arm64:*
microsoft windows_11_23h2 < 10.0.22631.3007 cpe:2.3:o:microsoft:windows_11_23h2:*:*:*:*:*:*:x64:*
microsoft windows_server_2022_23h2 — cpe:2.3:o:microsoft:windows_server_2022_23h2:-:*:*:*:*:*:*:*

References for CVE-2024-20697

cvelogic Threat Intelligence