# CVE-2008-5902: Memory corruption in n/a

> Remote attackers can execute arbitrary code via a crafted request due to a buffer overflow in the xrdp bitmap invalidation function.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/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:** 15 Jan 2009
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2008-5902, GHSA-j9gf-75xm-4w77

## What is CVE-2008-5902?

CVE-2008-5902 is a high-severity memory corruption vulnerability in n/a, published on 15 Jan 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow in the xrdp_bitmap_invalidate function in xrdp/xrdp_bitmap.c in xrdp 0.4.1 and earlier allows remote attackers to execute arbitrary code via a crafted request.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2008-5902?

It affects 1 product.


Products: Xrdp Xrdp.

## How do I fix CVE-2008-5902?

Upgrade to a fixed version.

## Is CVE-2008-5902 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-5903](https://insights.sbomify.com/CVE-2008-5903/): Memory corruption in n/a (high 7.5)
- [CVE-2008-5904](https://insights.sbomify.com/CVE-2008-5904/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-5902 and fix it if it is affected.

What it is: CVE-2008-5902 is a high-severity memory corruption vulnerability in n/a, published on 15 Jan 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-2008-5902 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-2008-5902/ (Markdown: https://insights.sbomify.com/CVE-2008-5902/index.md)
```

## Sources

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

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