CVE-2013-0211

Description

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.

Category

5.0
CVSS
Severity: Medium
CVSS 2.0 •
EPSS 1.20% Top 25%
Vendor Advisory freebsd.org Vendor Advisory mandriva.com Vendor Advisory opensuse.org Vendor Advisory fedoraproject.org Vendor Advisory ubuntu.com Vendor Advisory fedoraproject.org Vendor Advisory fedoraproject.org Vendor Advisory fedoraproject.org
Affected: n/a n/a
Published at:
Updated at:

References

Link Tags
https://github.com/libarchive/libarchive/commit/22531545514043e04633e1c015c7540b9de9dbe4 patch
https://www.freebsd.org/security/advisories/FreeBSD-SA-16:23.libarchive.asc third party advisory vendor advisory
http://www.mandriva.com/security/advisories?name=MDVSA-2013:147 third party advisory vendor advisory
http://lists.opensuse.org/opensuse-updates/2015-03/msg00065.html third party advisory vendor advisory
http://lists.fedoraproject.org/pipermail/package-announce/2013-April/101876.html third party advisory vendor advisory
http://www.securityfocus.com/bid/58926 vdb entry
https://bugzilla.redhat.com/show_bug.cgi?id=902998 patch issue tracking
http://www.securitytracker.com/id/1035995 third party advisory vdb entry
http://www.ubuntu.com/usn/USN-2549-1 third party advisory vendor advisory
http://lists.fedoraproject.org/pipermail/package-announce/2013-April/101687.html third party advisory vendor advisory
http://lists.fedoraproject.org/pipermail/package-announce/2013-April/101872.html third party advisory vendor advisory
http://lists.fedoraproject.org/pipermail/package-announce/2013-April/101700.html third party advisory vendor advisory

Frequently Asked Questions

What is the severity of CVE-2013-0211?
CVE-2013-0211 has been scored as a medium severity vulnerability.
How to fix CVE-2013-0211?
To fix CVE-2013-0211, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2013-0211 being actively exploited in the wild?
It is possible that CVE-2013-0211 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~1% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.