CVE-2016-4300
What it is
Integer overflow in the read_SubStreamsInfo function in archive_read_support_format_7zip.c in libarchive before 3.2.1 allows remote attackers to execute arbitrary code via a 7zip file with a large number of substreams, which triggers a heap-based buffer overflow.
At a glance
- Exploitability
- Can be exploited locally on the machine without logging in, but needs a user to act. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 4.9% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 4.9% in the next 30 days (EPSS).
- Severity: 7.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 4.9% · EPSS, next 30 days
- Weakness
- CWE-190 · Integer overflow
- Record status
- Modified
Affected
- Libarchive ≤ 3.2.0
- Redhat Enterprise Linux Desktop 7.0
- Redhat Enterprise Linux Hpc Node 7.0
- Redhat Enterprise Linux Hpc Node Eus 7.2
- Redhat Enterprise Linux Server 7.0
- Redhat Enterprise Linux Server Aus 7.2
- Redhat Enterprise Linux Server Eus 7.2
- Redhat Enterprise Linux Workstation 7.0
Attack profile CVSS 3.0 · 7.8
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2016-4300.md and follow it. Check whether this project is affected by CVE-2016-4300. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://github.com/libarchive/libarchive/commit/e79ef306afe332faf22e9b442a2c6b59cb175573
- https://github.com/libarchive/libarchive/issues/718
- https://github.com/libarchive/libarchive/commit/e79ef306afe332faf22e9b442a2c6b59cb175573
- https://github.com/libarchive/libarchive/issues/718
References
- http://blog.talosintel.com/2016/06/the-poisoned-archives.html
- http://rhn.redhat.com/errata/RHSA-2016-1844.html
- http://www.debian.org/security/2016/dsa-3657
- http://www.oracle.com/technetwork/topics/security/bulletinjul2016-3090568.html
- http://www.oracle.com/technetwork/topics/security/linuxbulletinjul2016-3090544.html
- http://www.securityfocus.com/bid/91326
- http://www.talosintel.com/reports/TALOS-2016-0152/
- https://bugzilla.redhat.com/show_bug.cgi?id=1348439
- https://github.com/libarchive/libarchive/commit/e79ef306afe332faf22e9b442a2c6b59cb175573
- https://github.com/libarchive/libarchive/issues/718
- https://security-center.intel.com/advisory.aspx?intelid=INTEL-SA-00062&languageid=en-fr
- https://security.gentoo.org/glsa/201701-03
- http://blog.talosintel.com/2016/06/the-poisoned-archives.html
- http://rhn.redhat.com/errata/RHSA-2016-1844.html
- http://www.debian.org/security/2016/dsa-3657
- http://www.oracle.com/technetwork/topics/security/bulletinjul2016-3090568.html
- http://www.oracle.com/technetwork/topics/security/linuxbulletinjul2016-3090544.html
- http://www.securityfocus.com/bid/91326
- http://www.talosintel.com/reports/TALOS-2016-0152/
- https://bugzilla.redhat.com/show_bug.cgi?id=1348439
- https://github.com/libarchive/libarchive/commit/e79ef306afe332faf22e9b442a2c6b59cb175573
- https://github.com/libarchive/libarchive/issues/718
- https://security-center.intel.com/advisory.aspx?intelid=INTEL-SA-00062&languageid=en-fr
- https://security.gentoo.org/glsa/201701-03