CVE-2013-4122
What it is
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.
At a glance
- Exploitability
- Can be exploited over the network without logging in. Limited direct impact.
- Exploit odds
- 3.6% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 3.6% in the next 30 days (EPSS).
- Severity: 4.3 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 3.6% · EPSS, next 30 days
- Weakness
- CWE-189
- Record status
- Modified
Affected
- Cmu cyrus-sasl ≤ 2.1.26
- Cmu cyrus-sasl 1.5.28
- Cmu cyrus-sasl 2.1.19
- Cmu cyrus-sasl 2.1.20
- Cmu cyrus-sasl 2.1.21
- Cmu cyrus-sasl 2.1.22
- Cmu cyrus-sasl 2.1.23
- Cmu cyrus-sasl 2.1.24
Attack profile CVSS 2.0 · 4.3
- Attack vector
- Network
- Complexity
- Medium
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Partial
Raw vector
AV:N/AC:M/Au:N/C:N/I:N/A:P
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2013-4122.md and follow it. Check whether this project is affected by CVE-2013-4122. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- http://git.cyrusimap.org/cyrus-sasl/commit/?id=dedad73e5e7a75d01a5f3d5a6702ab8ccd2ff40d
- http://git.cyrusimap.org/cyrus-sasl/commit/?id=dedad73e5e7a75d01a5f3d5a6702ab8ccd2ff40d
References
- http://git.cyrusimap.org/cyrus-sasl/commit/?id=dedad73e5e7a75d01a5f3d5a6702ab8ccd2ff40d
- http://security.gentoo.org/glsa/glsa-201309-01.xml
- http://www.debian.org/security/2015/dsa-3368
- http://www.openwall.com/lists/oss-security/2013/07/12/3
- http://www.openwall.com/lists/oss-security/2013/07/12/6
- http://www.openwall.com/lists/oss-security/2013/07/13/1
- http://www.openwall.com/lists/oss-security/2013/07/15/1
- http://www.ubuntu.com/usn/USN-2755-1
- https://www.linuxquestions.org/questions/slackware-14/%5Bslackware-current%5D-glibc-2-17-shadow-and-other-penumbrae-4175461061/
- http://git.cyrusimap.org/cyrus-sasl/commit/?id=dedad73e5e7a75d01a5f3d5a6702ab8ccd2ff40d
- http://security.gentoo.org/glsa/glsa-201309-01.xml
- http://www.debian.org/security/2015/dsa-3368
- http://www.openwall.com/lists/oss-security/2013/07/12/3
- http://www.openwall.com/lists/oss-security/2013/07/12/6
- http://www.openwall.com/lists/oss-security/2013/07/13/1
- http://www.openwall.com/lists/oss-security/2013/07/15/1
- http://www.ubuntu.com/usn/USN-2755-1
- https://www.linuxquestions.org/questions/slackware-14/%5Bslackware-current%5D-glibc-2-17-shadow-and-other-penumbrae-4175461061/