Skip to content
Fencer Intel
medium 5.0

CVE-2013-0211 json

Integer signedness error in the archive_write_zip_data function in archive_write_set_format_zip.c in libarchive 3.1.2 and earlier, when run…

published 13y ago modified 4mo ago also EUVD-2013-0246

cvss
5.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
3.9%
EPSS 3.9% chance of exploitation in 30 days, percentile 90%
public exploits
0
none known

Summary

Integer signedness error in the archive_write_zip_data function in archive_write_set_format_zip.c in libarchive 3.1.2 and earlier, when running on 64-bit machines, allows context-dependent attackers to cause a denial of service (crash) via unspecified vectors, which triggers an improper conversion between unsigned and signed types, leading to a buffer overflow.

Patch / fix

  • libarchive Debian 14, Debian 13, Debian 12 3.0.4-3

debian advisories DEBIAN-CVE-2013-0211

  • libarchive SLES for SAP 12, SLES 12, SLED 12 +1 more 3.1.2-9.1

suse advisories SUSE-SU-2015:0667-1

  • bsdtar openSUSE Tumbleweed 3.2.2-2.1

opensuse advisories openSUSE-SU-2024:10127-1

Is CVE-2013-0211 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-2013-0211 updated cvss 2.1

libarchive: read buffer overflow on 64-bit systems

  • Red Hat Enterprise Linux 6 libarchive
    affected: no fix planned “Will not fix”

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

3.93% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P

Classification

Weakness

References

Sources

Fencer Intel 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.