CVE-2024-57970

libarchive through 3.7.7 has a heap-based buffer over-read in header_gnu_longlink in archive_read_support_format_tar.c via a TAR archive because it mishandles truncation in the middle of a GNU long linkname.

Published: 2025-02-16 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-57970 is rated Low Risk (17/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.02%). Low composite risk—no urgent action required; patch on your normal maintenance cycle and revisit priority if CVSS or EPSS increases.

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-57970

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 0.07% 0.02% -0.06%
2 2025-11-18 0.04% 0.07% +0.03%
3 2025-02-16 — 0.04% —

Full EPSS history (3 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.0 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L 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:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 2.5 1.4 [email protected]

Weakness enumeration for CVE-2024-57970

OS Trackers for CVE-2024-57970

vendor priority summary link
alpine medium CVE-2024-57970: 1 source package rows (libarchive); 51 state rows across 6 repos (3.18-main, 3.19-main, 3.20-main, 3.21-main, 3.22-main, edge-main); fixed 6, open 45. https://security.alpinelinux.org/vuln/CVE-2024-57970
debian unimportant CVE-2024-57970 unimportant priority: Debian including 1 source packages (libarchive), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2024-57970
redhat medium — https://access.redhat.com/security/cve/CVE-2024-57970
suse medium CVE-2024-57970 severity moderate: SUSE including 12 source package names (bsdtar, bsdtar-3.7.7-2.1, …), 112 product×package rows across 36 product lines (SLES-LTSS-TERADATA 15 SP2, SUSE Linux Enterprise High Performance Computing 15 SP3-LTSS, … (36 product lines)): Known Not Affected 105, Fixed 7. https://www.suse.com/security/cve/CVE-2024-57970/
ubuntu medium CVE-2024-57970 medium priority: Ubuntu including 1 source packages (libarchive), 8 status rows across 8 suites (bionic, focal, jammy, noble, oracular, trusty, upstream, xenial): not-affected 8. https://ubuntu.com/security/CVE-2024-57970

Affected software / configurations for CVE-2024-57970

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2024-57970

cvelogic Threat Intelligence