What is the CVSS score of CVE-2016-10195?

CVE-2016-10195 has a CVSS 3.1 base score of 9.8 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 5.9%.

Is there a public PoC exploit available for CVE-2016-10195?

Yes, a public proof-of-concept exploit is available for CVE-2016-10195. Prioritise patching immediately. EPSS: 5.9%.

Is there a patch available for CVE-2016-10195?

Yes, a patch is available for CVE-2016-10195. Update the affected software to the latest version immediately.

Libevent CVE-2016-10195

CRITICAL

Out-of-bounds Read (CWE-125)

2017-03-15 cve@mitre.org

Buffer Overflow Information Disclosure Libevent Debian Linux

9.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

9.8 CRITICAL

AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

CVE Published

Mar 15, 2017 - 15:59 cve.org

CRITICAL 9.8

DescriptionCVE.org

AnalysisAI

The name_parse function in evdns.c in libevent before 2.1.6-beta allows remote attackers to have unspecified impact via vectors involving the label_len variable, which triggers an out-of-bounds stack. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available.

Technical ContextAI

This vulnerability is classified as Out-of-bounds Read (CWE-125), which allows attackers to read data from memory outside the intended buffer boundaries. The name_parse function in evdns.c in libevent before 2.1.6-beta allows remote attackers to have unspecified impact via vectors involving the label_len variable, which triggers an out-of-bounds stack read. Affected products include: Libevent Project Libevent, Debian Debian Linux. Version information: before 2.1.6.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Validate array indices and buffer lengths. Use memory-safe languages. Enable AddressSanitizer during testing.