Skip to content
Fencer Vulns
high 8.8

CVE-2020-9308 json

archive_read_support_format_rar5.c in libarchive before 3.4.2 attempts to unpack a RAR5 file with an invalid or corrupted header (such as a…

published 2020-02-20 6 y ago modified 2026-06-17 4 mo ago also EUVD-2020-30132

cvss
8.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.3%
EPSS 2.3% chance of exploitation in 30 days, percentile 83%
public exploits
0
none known

Summary

archive_read_support_format_rar5.c in libarchive before 3.4.2 attempts to unpack a RAR5 file with an invalid or corrupted header (such as a header size of zero), leading to a SIGSEGV or possibly unspecified other impact.

Patch / fix

  • libarchive libarchive 3.4.2
  • libarchive Debian 14, Debian 13, Debian 12 3.4.0-2

debian advisories DEBIAN-CVE-2020-9308

  • libarchive Alpine 3.24, Alpine 3.23, Alpine 3.22 +11 more 3.4.2-r0

alpine advisories ALPINE-CVE-2020-9308

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-9308 updated cvss 8.8

libarchive: attempts to unpack a RAR5 file with an invalid or corrupted header leads to a SIGSEGV

  • Red Hat Enterprise Linux 6 libarchive Red Hat Enterprise Linux 7 bsdtar, bsdcpio, libarchive Red Hat Enterprise Linux 8 bsdtar, libarchive
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.25% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.