CVE-2017-5437: High severity libevent libevent vulnerability
REJECT DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2016-10195, CVE-2016-10196, CVE-2016-10197. Reason: This candidate is a duplicate of CVE-2016-10195, CVE-2016-10196, and CVE-2016-10197. Notes: All CVE users should reference CVE-2016-10195, CVE-2016-10196, and/or CVE-2016-10197 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage.
Other sources
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2016-10195, CVE-2016-10196, CVE-2016-10197. Reason: This candidate is a duplicate of CVE-2016-10195, CVE-2016-10196, and CVE-2016-10197. Notes: All CVE users should reference CVE-2016-10195, CVE-2016-10196, and/or CVE-2016-10197 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage
— NVD
Three vulnerabilities in the <code>libevent</code> library allowing for out-of-bounds reads and denial of service (DoS) attacks.
— Red Hat
Affected Software
Event History
Frequently Asked Questions
What should I know about CVE-2017-5437?
CVE-2017-5437 is a rejected candidate and a duplicate of CVE-2016-10195, CVE-2016-10196, and CVE-2016-10197.
Which vulnerability IDs does CVE-2017-5437 relate to?
CVE-2017-5437 is related to CVE-2016-10195, CVE-2016-10196, and CVE-2016-10197.
Is CVE-2017-5437 still relevant for my security assessments?
CVE-2017-5437 is not relevant as it is marked as rejected and should not be used.
For vulnerabilities affecting Libevent, which CVE should I refer to?
For vulnerabilities affecting Libevent, refer to CVE-2016-10195, CVE-2016-10196, and CVE-2016-10197.
How should I handle security issues related to CVE-2017-5437?
Security issues related to CVE-2017-5437 should be assessed using the corresponding valid CVEs: CVE-2016-10195, CVE-2016-10196, and CVE-2016-10197.