CVE-2019-19221: In Libarchive 3.4.0, archive_wstring_append_from_mbs in archive_string.c has an out-of-bounds read because of an incorrect mbrtowc or mbtowc
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.65% (FIRST EPSS); higher than 50.8% of all records.
- Someone with local access to the system can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: libarchive-devel (AlmaLinux:8) 3.3.2-9.el8; libarchive (Alpine:v3.13) 3.4.2-r0; libarchive (Debian:10) 3.3.3-4+deb10u2.
Low priority for now. Upgrade to libarchive-devel (AlmaLinux:8) 3.3.2-9.el8; libarchive (Alpine:v3.13) 3.4.2-r0; libarchive (Debian:10) 3.3.3-4+deb10u2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In Libarchive 3.4.0, archive_wstring_append_from_mbs in archive_string.c has an out-of-bounds read because of an incorrect mbrtowc or mbtowc call. For example, bsdtar crashes via a crafted archive.
- Published
- Nov 21, 2019
- Updated
- Jun 16, 2026
- EPSS
- 0.6% · 50th percentile
- CWE
- CWE-125
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| libarchive | libarchive | cpe:2.3:a:libarchive:libarchive |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
| canonical | ubuntu linux | cpe:2.3:o:canonical:ubuntu_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- canonical ubuntu linux16.04
- canonical ubuntu linux18.04
- canonical ubuntu linux19.10
- debian debian linux10.0
- debian debian linux9.0
- fedoraproject fedora32
- libarchive libarchive3.4.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | libarchive-devel | before 3.3.2-9.el8 | 3.3.2-9.el8 |
| Alpine:v3.13 | libarchive | before 3.4.2-r0 | 3.4.2-r0 |
| Debian:10 | libarchive | before 3.3.3-4+deb10u2 | 3.3.3-4+deb10u2 |
| Debian:12 | libarchive | before 3.4.2-1 | 3.4.2-1 |
| Debian:9 | libarchive | before 3.2.2-2+deb9u3 | 3.2.2-2+deb9u3 |
| openSUSE:Tumbleweed | bsdtar | before 3.5.1-1.5 | 3.5.1-1.5 |
| Red Hat:enterprise_linux:8::baseos | bsdcat-debuginfo | before 0:3.3.2-9.el8 | 0:3.3.2-9.el8 |
| Red Hat:enterprise_linux:8::baseos | bsdcpio-debuginfo | before 0:3.3.2-9.el8 | 0:3.3.2-9.el8 |
| Red Hat:enterprise_linux:8::baseos | bsdtar | before 0:3.3.2-9.el8 | 0:3.3.2-9.el8 |
| Red Hat:enterprise_linux:8::baseos | bsdtar-debuginfo | before 0:3.3.2-9.el8 | 0:3.3.2-9.el8 |
| Red Hat:enterprise_linux:8::baseos | libarchive | before 0:3.3.2-9.el8 | 0:3.3.2-9.el8 |
| Red Hat:enterprise_linux:8::baseos | libarchive-debuginfo | before 0:3.3.2-9.el8 | 0:3.3.2-9.el8 |
| Red Hat:enterprise_linux:8::baseos | libarchive-debugsource | before 0:3.3.2-9.el8 | 0:3.3.2-9.el8 |
| Red Hat:enterprise_linux:8::crb | libarchive-devel | before 0:3.3.2-9.el8 | 0:3.3.2-9.el8 |
| SUSE:Linux Enterprise Software Development Kit 12 SP5 | libarchive | before 3.3.3-32.5.1 | 3.3.3-32.5.1 |
Same product
libarchive: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-26256Libarchive Remote Code Execution Vulnerability57Plan
- CVE-2022-36227In libarchive before 3.6.2, the software does not check for an error after calling calloc function that can return with a NULL pointer if th40Plan
- CVE-2016-1541Heap-based buffer overflow in the zip_read_mac_metadata function in archive_read_support_format_zip.c in libarchive before 3.2.0 allows remo38Monitor
Published before and after this one in the same product
- ← EarlierCVE-2019-11463Apr 22, 2019 · A memory leak in archive_read_format_zip_cleanup in archive_read_support_format_zip.c in libarchive 3.3.4-dev allows remote attackers to cau22Monitor
- ← EarlierCVE-2019-18408Oct 24, 2019 · archive_read_format_rar_read_data in archive_read_support_format_rar.c in libarchive before 3.4.0 has a use-after-free in a certain ARCHIVE_31Monitor
- Later →CVE-2020-9308Feb 20, 2020 · 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 36Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| almalinux:libarchive-devel | 3.3.2-9.el8 · AlmaLinux:8 | Package registry (OSV) |
| alpine:libarchive | 3.4.2-r0 · Alpine:v3.13 | Package registry (OSV) |
| debian:libarchive | 3.4.2-1 · Debian:12 | Package registry (OSV) |
| opensuse:bsdtar | 3.5.1-1.5 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:bsdcat-debuginfo | 0:3.3.2-9.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:bsdcpio-debuginfo | 0:3.3.2-9.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:bsdtar | 0:3.3.2-9.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:bsdtar-debuginfo | 0:3.3.2-9.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:libarchive | 0:3.3.2-9.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:libarchive-debuginfo | 0:3.3.2-9.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:libarchive-debugsource | 0:3.3.2-9.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:libarchive-devel | 0:3.3.2-9.el8 · Red Hat:enterprise_linux:8::crb | Package registry (OSV) |
| suse:libarchive | 3.3.3-32.5.1 · SUSE:Linux Enterprise Software Development Kit 12 SP5 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-125 · Out-of-bounds ReadCVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.