PatchTheCVElibevent project vulnerabilities
Recent CVEs affecting libevent project products. 5 tracked.
libevent project has 5 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 3. Most recent: 2017-03-15. Highest priority: CVE-2016-10195 (score 73/100).
- CVE-2016-10197 HIGH 7.5 MITIGATE UPGRADE The search_make_new function in evdns.c in libevent before 2.1.6-beta allows attackers to cause a denial of se
- CVE-2016-10196 HIGH 7.5 MITIGATE UPGRADE Stack-based buffer overflow in the evutil_parse_sockaddr_port function in evutil.c in libevent before 2.1.6-be
- CVE-2016-10195 CRITICAL 9.8 UPGRADE MITIGATE The name_parse function in evdns.c in libevent before 2.1.6-beta allows remote attackers to have unspecified i
- CVE-2015-6525 HIGH 7.5 MITIGATE DOWNGRADE Multiple integer overflows in the evbuffer API in Libevent 2.0.x before 2.0.22 and 2.1.x before 2.1.5-beta all
- CVE-2014-6272 HIGH 7.5 MITIGATE DOWNGRADE 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
FAQ
How do I fix libevent project vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is libevent project being exploited right now?
None of the tracked libevent project CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which libevent project CVE should I patch first?
CVE-2016-10195 currently ranks highest (73/100): The name_parse function in evdns.c in libevent before 2.1.6-beta allows remote attackers to have unspecified i.