CVE-2015-5291

UnknownEPSS 3.63%

Last modified

CVE-2015-5291 is a vulnerability of currently unknown severity. Heap-based buffer overflow in PolarSSL 1.x before 1.2.17 and ARM mbed TLS (formerly PolarSSL) 1.3.x before 1.3.14 and 2.x before 2.1.2 allows remote SSL servers to cause a denial of service (client crash) and possibly execute arbitrary code via a long hostname to the server name indication (SNI) extension, which is not properly handled when creating a ClientHello message. NOTE: this identifier has been SPLIT per ADT3 due to different affected version ranges. EPSS estimates a 3.63% chance of exploitation in the next 30 days.

Description

Heap-based buffer overflow in PolarSSL 1.x before 1.2.17 and ARM mbed TLS (formerly PolarSSL) 1.3.x before 1.3.14 and 2.x before 2.1.2 allows remote SSL servers to cause a denial of service (client crash) and possibly execute arbitrary code via a long hostname to the server name indication (SNI) extension, which is not properly handled when creating a ClientHello message. NOTE: this identifier has been SPLIT per ADT3 due to different affected version ranges. See CVE-2015-8036 for the session ticket issue that was introduced in 1.3.0.

Metrics

EPSS Probability
3.63%

88.1th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
PolarsslPolarssl>= 1.0.0, < 1.2.17
TrustedfirmwareMbed Tls>= 1.3.0, < 1.3.14
TrustedfirmwareMbed Tls>= 2.0.0, < 2.1.2
DebianDebian Linux7.0
DebianDebian Linux8.0
FedoraprojectFedora21
FedoraprojectFedora22
FedoraprojectFedora23
OpensuseLeap42.1
OpensuseOpensuse13.2

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2015-5291?
Heap-based buffer overflow in PolarSSL 1.x before 1.2.17 and ARM mbed TLS (formerly PolarSSL) 1.3.x before 1.3.14 and 2.x before 2.1.2 allows remote SSL servers to cause a denial of service (client crash) and possibly execute arbitrary code via a long hostname to the server name indication (SNI) extension, which is not properly handled when creating a ClientHello message. NOTE: this identifier has been SPLIT per ADT3 due to different affected version ranges. See CVE-2015-8036 for the session ticket issue that was introduced in 1.3.0.
How severe is CVE-2015-5291?
Severity scoring for CVE-2015-5291 is pending analysis. The EPSS model estimates a 3.63% probability of exploitation in the next 30 days.
How do I fix CVE-2015-5291?
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-2015-5291?

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

Scan your code now

Source: NVD / NIST