Strix
26.1K

CVE-2016-0798

UnknownEPSS 24.41%

Last modified

CVE-2016-0798 is a vulnerability of currently unknown severity. Memory leak in the SRP_VBASE_get_by_user implementation in OpenSSL 1.0.1 before 1.0.1s and 1.0.2 before 1.0.2g allows remote attackers to cause a denial of service (memory consumption) by providing an invalid username in a connection attempt, related to apps/s_server.c and crypto/srp/srp_vfy.c.. EPSS estimates a 24.41% chance of exploitation in the next 30 days.

Description

Memory leak in the SRP_VBASE_get_by_user implementation in OpenSSL 1.0.1 before 1.0.1s and 1.0.2 before 1.0.2g allows remote attackers to cause a denial of service (memory consumption) by providing an invalid username in a connection attempt, related to apps/s_server.c and crypto/srp/srp_vfy.c.

Metrics

EPSS Probability
24.41%

97.6th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
OpensslOpenssl1.0.1
OpensslOpenssl1.0.1a
OpensslOpenssl1.0.1b
OpensslOpenssl1.0.1c
OpensslOpenssl1.0.1d
OpensslOpenssl1.0.1e
OpensslOpenssl1.0.1f
OpensslOpenssl1.0.1g
OpensslOpenssl1.0.1h
OpensslOpenssl1.0.1i
OpensslOpenssl1.0.1j
OpensslOpenssl1.0.1k
OpensslOpenssl1.0.1l
OpensslOpenssl1.0.1m
OpensslOpenssl1.0.1n
OpensslOpenssl1.0.1o
OpensslOpenssl1.0.1p
OpensslOpenssl1.0.1q
OpensslOpenssl1.0.1r
OpensslOpenssl1.0.2
OpensslOpenssl1.0.2a
OpensslOpenssl1.0.2b
OpensslOpenssl1.0.2c
OpensslOpenssl1.0.2d
OpensslOpenssl1.0.2e
OpensslOpenssl1.0.2f

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2016-0798?
Memory leak in the SRP_VBASE_get_by_user implementation in OpenSSL 1.0.1 before 1.0.1s and 1.0.2 before 1.0.2g allows remote attackers to cause a denial of service (memory consumption) by providing an invalid username in a connection attempt, related to apps/s_server.c and crypto/srp/srp_vfy.c.
How severe is CVE-2016-0798?
Severity scoring for CVE-2016-0798 is pending analysis. The EPSS model estimates a 24.41% probability of exploitation in the next 30 days.
How do I fix CVE-2016-0798?
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-2016-0798?

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

Scan your code now

Source: NVD / NIST