CVE-2015-3216

UnknownEPSS 4.30%

Last modified

CVE-2015-3216 is a vulnerability of currently unknown severity. Race condition in a certain Red Hat patch to the PRNG lock implementation in the ssleay_rand_bytes function in OpenSSL, as distributed in openssl-1.0.1e-25.el7 in Red Hat Enterprise Linux (RHEL) 7 and other products, allows remote attackers to cause a denial of service (application crash) by establishing many TLS sessions to a multithreaded server, leading to use of a negative value for a certain length field.. EPSS estimates a 4.30% chance of exploitation in the next 30 days.

Description

Race condition in a certain Red Hat patch to the PRNG lock implementation in the ssleay_rand_bytes function in OpenSSL, as distributed in openssl-1.0.1e-25.el7 in Red Hat Enterprise Linux (RHEL) 7 and other products, allows remote attackers to cause a denial of service (application crash) by establishing many TLS sessions to a multithreaded server, leading to use of a negative value for a certain length field.

Metrics

EPSS Probability
4.30%

89.9th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
RedhatEnterprise Linux7.0
OpensslOpenssl1.0.1e-25.el7

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2015-3216?
Race condition in a certain Red Hat patch to the PRNG lock implementation in the ssleay_rand_bytes function in OpenSSL, as distributed in openssl-1.0.1e-25.el7 in Red Hat Enterprise Linux (RHEL) 7 and other products, allows remote attackers to cause a denial of service (application crash) by establishing many TLS sessions to a multithreaded server, leading to use of a negative value for a certain length field.
How severe is CVE-2015-3216?
Severity scoring for CVE-2015-3216 is pending analysis. The EPSS model estimates a 4.30% probability of exploitation in the next 30 days.
How do I fix CVE-2015-3216?
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-3216?

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

Scan your code now

Source: NVD / NIST