CVE-2017-2800 Memory corruption in wolfSSL

High 8.1 Published Updated

A crafted x509 certificate causes an out-of-bounds write in wolfSSL, potentially allowing remote code execution or denial of service.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2017-2800?

CVE-2017-2800 is a high-severity memory corruption vulnerability in Wolfssl Wolfssl, published on 24 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official 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.

Weakness: CWE-295

Which versions are affected by CVE-2017-2800?

It affects 1 product.

Products include Wolfssl Wolfssl.

How do I fix CVE-2017-2800?

Upgrade to a fixed version.

Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.

Is CVE-2017-2800 being exploited?

There is no known exploitation of CVE-2017-2800 in the wild and no public exploit code.

Public exploit code: 1 Exploit-DB entry.

All Wolfssl Wolfssl vulnerabilities

Sources

Also known as DEBIAN-CVE-2017-2800, GHSA-59h3-rq7p-jqmv, UBUNTU-CVE-2017-2800.

Is CVE-2017-2800 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free