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

> Remote attackers can crash the EMC Dantz Retrospect Backup Client daemon by sending malformed packets, causing a denial of service.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jul 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-w75g-pf4w-q85j

## What is CVE-2008-3290?

CVE-2008-3290 is a medium-severity memory corruption vulnerability in n/a, published on 24 Jul 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

retroclient.exe in EMC Dantz Retrospect Backup Client 7.5.116 allows remote attackers to cause a denial of service (daemon crash) via a series of long packets containing 0x00 characters to TCP port 497 that trigger memory corruption, probably involving an English product version on a Chinese OS version.

Weakness: CWE-399

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

It affects 1 product.


Products: Emc Dantz Retrospect Backup Client.

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

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

## Is CVE-2008-3290 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-3287](https://insights.sbomify.com/CVE-2008-3287/): Null dereference in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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