# CVE-2004-0389: Null dereference in n/a

> Remote attackers can crash the Helix Universal Server by sending malformed GET_PARAMETER or DESCRIBE requests, causing a denial of service.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Apr 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-rc8v-wc74-5x2x

## What is CVE-2004-0389?

CVE-2004-0389 is a high-severity vulnerability in n/a, published on 17 Apr 2004. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

RealNetworks Helix Universal Server 9.0.1 and 9.0.2 allows remote attackers to cause a denial of service (crash) via malformed requests that trigger a null dereference, as demonstrated using (1) GET_PARAMETER or (2) DESCRIBE requests.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2004-0389?

It affects 1 product.


Products: Realnetworks Helix Universal Server.

## How do I fix CVE-2004-0389?

No fix has been published for CVE-2004-0389 yet. Limit exposure of the affected software until one is available.

## Is CVE-2004-0389 being exploited?

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

Public exploit code:

- Real Networks Helix Universal Server 9.0.x - Denial of Service (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2002-1643](https://insights.sbomify.com/CVE-2002-1643/): Memory corruption in n/a (high 7.5)
- [CVE-2003-0725](https://insights.sbomify.com/CVE-2003-0725/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-0389 and fix it if it is affected.

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

## Sources

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

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