# CVE-2008-6219: Denial of service in n/a

> Remote attackers can cause denial of service in EMC NetWorker products by sending crafted RPC requests that exhaust memory.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Feb 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-7p22-rr7f-4rjq

## What is CVE-2008-6219?

CVE-2008-6219 is a high-severity denial of service vulnerability in n/a, published on 20 Feb 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

nsrexecd.exe in multiple EMC Networker products including EMC NetWorker Server, Storage Node, and Client 7.3.x and 7.4, 7.4.1, 7.4.2, Client and Storage Node for Open VMS 7.3.2 ECO6 and earlier, Module for Microsoft Exchange 5.1 and earlier, Module for Microsoft Applications 2.0 and earlier, Module for Meditech 2.0 and earlier, and PowerSnap 2.4 SP1 and earlier does not properly control the allocation of memory, which allows remote attackers to cause a denial of service (memory exhaustion) via multiple crafted RPC requests.

Weakness: CWE-399

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

It affects 5 products.


Products: Emc Networker Client, Emc Networker Module, Emc Networker Powersnap, Emc Networker Server, Emc Networker Storage Node.

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

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

## Is CVE-2008-6219 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2008-6219 is a high-severity denial of service vulnerability in n/a, published on 20 Feb 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-6219 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-6219/ (Markdown: https://insights.sbomify.com/CVE-2008-6219/index.md)
```

## Sources

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

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