CVE-2014-6272
What it is
Multiple integer overflows in the evbuffer API in Libevent 1.4.x before 1.4.15, 2.0.x before 2.0.22, and 2.1.x before 2.1.5-beta allow context-dependent attackers to cause a denial of service or possibly have other unspecified impact via "insanely large inputs" to the (1) evbuffer_add, (2) evbuffer_expand, or (3) bufferevent_write function, which triggers a heap-based buffer overflow or an infinite loop. NOTE: this identifier has been SPLIT per ADT3 due to different affected versions. See CVE-2015-6525 for the functions that are only affected in 2.0 and later.
At a glance
- Exploitability
- Can be exploited over the network without logging in. Limited direct impact.
- Exploit odds
- 2.1% 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: 2.1% in the next 30 days (EPSS).
- Severity: 7.5 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 2.1% · EPSS, next 30 days
- Weakness
- CWE-189
- Record status
- Modified
Affected
- Debian Linux 7.0
- Libevent Project Libevent 1.4.0
- Libevent Project Libevent 1.4.1
- Libevent Project Libevent 1.4.2
- Libevent Project Libevent 1.4.3
- Libevent Project Libevent 1.4.4
- Libevent Project Libevent 1.4.5
- Libevent Project Libevent 1.4.6
Attack profile CVSS 2.0 · 7.5
- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
Raw vector
AV:N/AC:L/Au:N/C:P/I:P/A:P
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-2014-6272.md and follow it. Check whether this project is affected by CVE-2014-6272. 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
- http://archives.seul.org/libevent/users/Jan-2015/msg00010.html
- http://archives.seul.org/libevent/users/Jan-2015/msg00010.html
References
- http://archives.seul.org/libevent/users/Jan-2015/msg00010.html
- http://www.debian.org/security/2015/dsa-3119
- http://www.slackware.com/security/viewer.php?l=slackware-security&y=2016&m=slackware-security.366317
- https://puppet.com/security/cve/CVE-2014-6272
- http://archives.seul.org/libevent/users/Jan-2015/msg00010.html
- http://www.debian.org/security/2015/dsa-3119
- http://www.slackware.com/security/viewer.php?l=slackware-security&y=2016&m=slackware-security.366317
- https://puppet.com/security/cve/CVE-2014-6272