# CVE-2013-4122: Null dereference in n/a

> Remote attackers can cause a denial of service in Cyrus SASL via a NULL pointer dereference triggered by invalid salts or specific encrypted passwords.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Oct 2013
- **Updated:** 6 Aug 2024
- **Also known as:** ALPINE-CVE-2013-4122, CLEANSTART-2024-XI23677, DEBIAN-CVE-2013-4122, DSA-3368-1, GHSA-pwpx-m778-r79w

## What is CVE-2013-4122?

CVE-2013-4122 is a medium-severity vulnerability in n/a, published on 27 Oct 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-189

## Which versions are affected by CVE-2013-4122?

It affects 1 product.


Products: Cmu Cyrus-Sasl.

## How do I fix CVE-2013-4122?

Apply the vendor's patch.

## Is CVE-2013-4122 being exploited?

There is no known exploitation of CVE-2013-4122 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-4122 and fix it if it is affected.

What it is: CVE-2013-4122 is a medium-severity vulnerability in n/a, published on 27 Oct 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-4122 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2013-4122/ (Markdown: https://insights.sbomify.com/CVE-2013-4122/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2013-4122
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-4122
- OSV: https://osv.dev/vulnerability/CVE-2013-4122

---
From sbomify Insights: https://insights.sbomify.com/CVE-2013-4122/
Summaries are generated and may contain mistakes; the official description above is the record.