CVE-2024-48958
Libarchive out-of-bounds read
- Published10 Oct 2024
Description
execute_filter_delta in archive_read_support_format_rar.c in libarchive before 3.7.5 allows out-of-bounds access via a crafted archive file because src can move beyond dst.
CVSS 3.1 breakdown
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HAffected products
Remediation
References
- http://seclists.org/fulldisclosure/2025/Apr/11
- http://seclists.org/fulldisclosure/2025/Apr/12
- http://seclists.org/fulldisclosure/2025/Apr/13
- http://seclists.org/fulldisclosure/2025/Apr/4
- http://seclists.org/fulldisclosure/2025/Apr/8
- https://github.com/libarchive/libarchive/compare/v3.7.4...v3.7.5
- https://github.com/libarchive/libarchive/pull/2148
- https://github.com/terrynini/CVE-Reports/tree/main/CVE-2024-48958
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2024-48958 being actively exploited?
CVE-2024-48958 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.55%.
How severe is CVE-2024-48958?
CVE-2024-48958 has a CVSS 3.1 base score of 7.8, rated high. EPSS estimates a 0.55% probability of exploitation.
Which products are affected by CVE-2024-48958?
Affected products include Libarchive.
How do I fix CVE-2024-48958?
Upgrade affected software to a fixed version, for example Libarchive 3.7.5 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2024-48958 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.