# CVE-2010-1152: Denial of service in n/a

> Remote attackers can cause a denial of service in memcached by sending a long line that triggers excessive memory allocation, crashing or hanging the daemon.

- **Severity:** Medium 5.0 (`AV:N/AC:L/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:** 12 Apr 2010
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2010-1152, GHSA-jp9p-pjv6-qv68

## What is CVE-2010-1152?

CVE-2010-1152 is a medium-severity denial of service vulnerability in n/a, published on 12 Apr 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

memcached.c in memcached before 1.4.3 allows remote attackers to cause a denial of service (daemon hang or crash) via a long line that triggers excessive memory allocation.  NOTE: some of these details are obtained from third party information.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2010-1152?

It affects 1 product.


Products: Memcachedb Memcached.

## How do I fix CVE-2010-1152?

Upgrade to a fixed version.

## Is CVE-2010-1152 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2010-1152 exists.

Public exploit code:

- memcached 1.4.2 - Memory Consumption Remote Denial of Service (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2009-2415](https://insights.sbomify.com/CVE-2009-2415/): Integer overflow in n/a (critical 10.0)
- [CVE-2009-1255](https://insights.sbomify.com/CVE-2009-1255/): Information disclosure in n/a (medium 5.0)
- [CVE-2009-1494](https://insights.sbomify.com/CVE-2009-1494/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-1152 and fix it if it is affected.

What it is: CVE-2010-1152 is a medium-severity denial of service vulnerability in n/a, published on 12 Apr 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2010-1152 exists.

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-2010-1152/ (Markdown: https://insights.sbomify.com/CVE-2010-1152/index.md)
```

## Sources

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

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