CVE-2015-2695

UnknownEPSS 6.24%

Last modified

CVE-2015-2695 is a vulnerability of currently unknown severity. lib/gssapi/spnego/spnego_mech.c in MIT Kerberos 5 (aka krb5) before 1.14 relies on an inappropriate context handle, which allows remote attackers to cause a denial of service (incorrect pointer read and process crash) via a crafted SPNEGO packet that is mishandled during a gss_inquire_context call.. EPSS estimates a 6.24% chance of exploitation in the next 30 days.

Description

lib/gssapi/spnego/spnego_mech.c in MIT Kerberos 5 (aka krb5) before 1.14 relies on an inappropriate context handle, which allows remote attackers to cause a denial of service (incorrect pointer read and process crash) via a crafted SPNEGO packet that is mishandled during a gss_inquire_context call.

Metrics

EPSS Probability
6.24%

92.6th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersionsUpdate
MitKerberos 5< 1.14
OracleSolaris11.3
CanonicalUbuntu Linux12.04
CanonicalUbuntu Linux14.04
CanonicalUbuntu Linux15.04
CanonicalUbuntu Linux15.10
DebianDebian Linux7.0
DebianDebian Linux8.0
DebianDebian Linux9.0
OpensuseLeap42.1
OpensuseOpensuse13.1
OpensuseOpensuse13.2
SuseLinux Enterprise Desktop11Sp3
SuseLinux Enterprise Desktop12
SuseLinux Enterprise Server11Sp3
SuseLinux Enterprise Server12
SuseLinux Enterprise Software Development Kit11Sp3
SuseLinux Enterprise Software Development Kit12

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2015-2695?
lib/gssapi/spnego/spnego_mech.c in MIT Kerberos 5 (aka krb5) before 1.14 relies on an inappropriate context handle, which allows remote attackers to cause a denial of service (incorrect pointer read and process crash) via a crafted SPNEGO packet that is mishandled during a gss_inquire_context call.
How severe is CVE-2015-2695?
Severity scoring for CVE-2015-2695 is pending analysis. The EPSS model estimates a 6.24% probability of exploitation in the next 30 days.
How do I fix CVE-2015-2695?
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-2695?

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

Scan your code now

Source: NVD / NIST