# CVE-2009-1255: Information disclosure in n/a

> Remote attackers can retrieve memory layout and allocation stats via stats commands, exposing sensitive data and defeating ASLR protections.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Apr 2009
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2009-1255, GHSA-29xr-pwpr-24h3

## What is CVE-2009-1255?

CVE-2009-1255 is a medium-severity vulnerability in n/a, published on 30 Apr 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The process_stat function in (1) Memcached before 1.2.8 and (2) MemcacheDB 1.2.0 discloses (a) the contents of /proc/self/maps in response to a stats maps command and (b) memory-allocation statistics in response to a stats malloc command, which allows remote attackers to obtain sensitive information such as the locations of memory regions, and defeat ASLR protection, by sending a command to the daemon's TCP port.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2009-1255?

It affects 1 product.


Products: Memcachedb Memcached.

## How do I fix CVE-2009-1255?

Upgrade to a fixed version.

## Is CVE-2009-1255 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-2415](https://insights.sbomify.com/CVE-2009-2415/): Integer overflow in n/a (critical 10.0)
- [CVE-2010-1152](https://insights.sbomify.com/CVE-2010-1152/): Denial of service 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-2009-1255 and fix it if it is affected.

What it is: CVE-2009-1255 is a medium-severity vulnerability in n/a, published on 30 Apr 2009. 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-2009-1255 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-2009-1255/ (Markdown: https://insights.sbomify.com/CVE-2009-1255/index.md)
```

## Sources

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

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