What is the severity of CVE-2017-2800?

CVE-2017-2800 is considered a high severity vulnerability due to its potential for denial of service and remote code execution.

How do I fix CVE-2017-2800?

To mitigate CVE-2017-2800, upgrade wolfSSL to version 3.10.3 or later.

Which versions of wolfSSL are affected by CVE-2017-2800?

All versions of wolfSSL up to and including 3.10.2 are affected by CVE-2017-2800.

What kind of attack can exploit CVE-2017-2800?

An attacker can exploit CVE-2017-2800 by supplying a specially crafted x509 certificate.

Vulnerability/
CVE-2017-2800

critical

9.8

CWE

295

24/5/2017

5/8/2024

CVE-2017-2800

Q: What types of vulnerabilities are associated with CVE-2017-2800?

CVE-2017-2800 can result in certificate validation vulnerabilities, denial of service, and possible remote code execution.

First published: Wed May 24 2017(Updated: )

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.

Credit: talos-cna@cisco.com

Affected Software	Affected Version	How to fix
wolfSSL	<=3.10.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-2800?
CVE-2017-2800 is considered a high severity vulnerability due to its potential for denial of service and remote code execution.
How do I fix CVE-2017-2800?
To mitigate CVE-2017-2800, upgrade wolfSSL to version 3.10.3 or later.
What types of vulnerabilities are associated with CVE-2017-2800?
CVE-2017-2800 can result in certificate validation vulnerabilities, denial of service, and possible remote code execution.
Which versions of wolfSSL are affected by CVE-2017-2800?
All versions of wolfSSL up to and including 3.10.2 are affected by CVE-2017-2800.
What kind of attack can exploit CVE-2017-2800?
An attacker can exploit CVE-2017-2800 by supplying a specially crafted x509 certificate.

agent/references
agent/type
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/author
agent/severity
agent/weakness
agent/description
agent/event
agent/first-publish-date
agent/softwarecombine
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/wolfssl
canonical/wolfssl
version/wolfssl/3.10.2

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2017-2800?
CVE-2017-2800 is considered a high severity vulnerability due to its potential for denial of service and remote code execution.
How do I fix CVE-2017-2800?
To mitigate CVE-2017-2800, upgrade wolfSSL to version 3.10.3 or later.
What types of vulnerabilities are associated with CVE-2017-2800?
CVE-2017-2800 can result in certificate validation vulnerabilities, denial of service, and possible remote code execution.
Which versions of wolfSSL are affected by CVE-2017-2800?
All versions of wolfSSL up to and including 3.10.2 are affected by CVE-2017-2800.
What kind of attack can exploit CVE-2017-2800?
An attacker can exploit CVE-2017-2800 by supplying a specially crafted x509 certificate.