CVE-2017-2800

CRITICALCVSS 9.8/10EPSS 8.53%

Last modified

CVE-2017-2800 is a critical-severity vulnerability rated 9.8/10 on the CVSS scale. A specially crafted x509 certificate can cause a single out of bounds byte overwrite in wolfSSL through 3.10.2 resulting in potential certificate validation vulnerabilities, denial of service and possible remote code execution. In order to trigger this vulnerability, the attacker needs to supply a malicious x509 certificate to either a server or a client application using this library.. EPSS estimates a 8.53% chance of exploitation in the next 30 days.

Description

A specially crafted x509 certificate can cause a single out of bounds byte overwrite in wolfSSL through 3.10.2 resulting in potential certificate validation vulnerabilities, denial of service and possible remote code execution. In order to trigger this vulnerability, the attacker needs to supply a malicious x509 certificate to either a server or a client application using this library.

Metrics

CVSS 3.1
9.8/10

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

EPSS Probability
8.53%

94.4th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
WolfsslWolfssl<= 3.10.2

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2017-2800?
A specially crafted x509 certificate can cause a single out of bounds byte overwrite in wolfSSL through 3.10.2 resulting in potential certificate validation vulnerabilities, denial of service and possible remote code execution. In order to trigger this vulnerability, the attacker needs to supply a malicious x509 certificate to either a server or a client application using this library.
How severe is CVE-2017-2800?
CVE-2017-2800 has a CVSS score of 9.8/10 (CRITICAL severity). The EPSS model estimates a 8.53% probability of exploitation in the next 30 days.
How do I fix CVE-2017-2800?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2017-2800?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST