Strix
26.1K

CVE-2013-4122

UnknownEPSS 3.59%

Last modified

CVE-2013-4122 is a vulnerability of currently unknown severity. Cyrus SASL 2.1.23, 2.1.26, and earlier does not properly handle when a NULL value is returned upon an error by the crypt function as implemented in glibc 2.17 and later, which allows remote attackers to cause a denial of service (thread crash and consumption) via (1) an invalid salt or, when FIPS-140 is enabled, a (2) DES or (3) MD5 encrypted password, which triggers a NULL pointer dereference.. EPSS estimates a 3.59% chance of exploitation in the next 30 days.

Description

Cyrus SASL 2.1.23, 2.1.26, and earlier does not properly handle when a NULL value is returned upon an error by the crypt function as implemented in glibc 2.17 and later, which allows remote attackers to cause a denial of service (thread crash and consumption) via (1) an invalid salt or, when FIPS-140 is enabled, a (2) DES or (3) MD5 encrypted password, which triggers a NULL pointer dereference.

Metrics

EPSS Probability
3.59%

87.9th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
CmuCyrus-Sasl<= 2.1.26
CmuCyrus-Sasl1.5.28
CmuCyrus-Sasl2.1.19
CmuCyrus-Sasl2.1.20
CmuCyrus-Sasl2.1.21
CmuCyrus-Sasl2.1.22
CmuCyrus-Sasl2.1.23
CmuCyrus-Sasl2.1.24
CmuCyrus-Sasl2.1.25

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2013-4122?
Cyrus SASL 2.1.23, 2.1.26, and earlier does not properly handle when a NULL value is returned upon an error by the crypt function as implemented in glibc 2.17 and later, which allows remote attackers to cause a denial of service (thread crash and consumption) via (1) an invalid salt or, when FIPS-140 is enabled, a (2) DES or (3) MD5 encrypted password, which triggers a NULL pointer dereference.
How severe is CVE-2013-4122?
Severity scoring for CVE-2013-4122 is pending analysis. The EPSS model estimates a 3.59% probability of exploitation in the next 30 days.
How do I fix CVE-2013-4122?
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.

How Strix Helps

Related CVEs from 2013

View all 2013CVEs →

Are you affected by CVE-2013-4122?

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

Scan your code now

Source: NVD / NIST