# CVE-2013-7239: Auth bypass in n/a

> Remote attackers can bypass SASL authentication in memcached by sending specific invalid and incorrect credential requests, requiring SASL to be enabled.

- **Severity:** Medium 4.8 (`AV:A/AC:L/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Jan 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2013-7239, GHSA-v5qw-pp2p-cvpr

## What is CVE-2013-7239?

CVE-2013-7239 is a medium-severity authentication bypass vulnerability in n/a, published on 13 Jan 2014. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

memcached before 1.4.17 allows remote attackers to bypass authentication by sending an invalid request with SASL credentials, then sending another request with incorrect SASL credentials.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Memcached Memcached.

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

Upgrade to a fixed version.

## Is CVE-2013-7239 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-46853](https://insights.sbomify.com/CVE-2023-46853/): Memory corruption in n/a (critical 9.8)
- [CVE-2016-8704](https://insights.sbomify.com/CVE-2016-8704/): Integer overflow in Memcached (critical 9.8)
- [CVE-2016-8705](https://insights.sbomify.com/CVE-2016-8705/): Integer overflow in Memcached (critical 9.8)
- [CVE-2026-47783](https://insights.sbomify.com/CVE-2026-47783/): Information disclosure in memcached (high 8.1)
- [CVE-2026-47784](https://insights.sbomify.com/CVE-2026-47784/): Information disclosure in memcached (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-7239 is a medium-severity authentication bypass vulnerability in n/a, published on 13 Jan 2014. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-7239 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-7239/ (Markdown: https://insights.sbomify.com/CVE-2013-7239/index.md)
```

## Sources

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

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