# CVE-2005-2922: Memory corruption in n/a

> Remote attackers can trigger a heap buffer overflow in RealNetworks players via malicious HTTP responses, potentially causing crashes or arbitrary code execution.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 23 Mar 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-w8fj-r9j2-qg46

## What is CVE-2005-2922?

CVE-2005-2922 is a critical memory corruption vulnerability in Realnetworks Realplayer, published on 23 Mar 2006. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Heap-based buffer overflow in the embedded player in multiple RealNetworks products and versions including RealPlayer 10.x, RealOne Player, and Helix Player allows remote malicious servers to cause a denial of service (crash) and possibly execute arbitrary code via a chunked Transfer-Encoding HTTP response in which either (1) the chunk header length is specified as -1, (2) the chunk header with a length that is less than the actual amount of sent data, or (3) a missing chunk header.

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

## Which versions are affected by CVE-2005-2922?

It affects 4 products.


Products: Realnetworks Helix Player, Realnetworks Realone Player, Realnetworks Realplayer, Realnetworks Rhapsody.

## How do I fix CVE-2005-2922?

Apply the vendor's patch.

## Is CVE-2005-2922 being exploited?

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

## Other vulnerabilities in Realnetworks Realplayer

- [CVE-2009-4241](https://insights.sbomify.com/CVE-2009-4241/): Memory corruption in n/a (critical 9.3)
- [CVE-2009-4242](https://insights.sbomify.com/CVE-2009-4242/): Memory corruption in n/a (critical 9.3)
- [CVE-2009-4243](https://insights.sbomify.com/CVE-2009-4243/): Memory corruption in n/a (critical 9.3)
- [CVE-2009-4244](https://insights.sbomify.com/CVE-2009-4244/): Memory corruption in n/a (critical 9.3)
- [CVE-2009-4245](https://insights.sbomify.com/CVE-2009-4245/): Memory corruption in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-2922 and fix it if it is affected.

What it is: CVE-2005-2922 is a critical memory corruption vulnerability in Realnetworks Realplayer, published on 23 Mar 2006. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2005-2922 in the wild and no public exploit code.

Affected product: Realnetworks Realplayer. 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-2005-2922/ (Markdown: https://insights.sbomify.com/CVE-2005-2922/index.md)
```

## Sources

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

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