# CVE-2006-6076: Memory corruption in n/a

> Remote attackers can execute arbitrary code via RPC requests to the Tape Engine in CA BrightStor ARCserve Backup.

- **Severity:** Critical 10.0 (`AV:N/AC:L/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:** Not needed
- **Fix available:** No
- **Published:** 24 Nov 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-f4wf-c423-fr3w

## What is CVE-2006-6076?

CVE-2006-6076 is a critical memory corruption vulnerability in n/a, published on 24 Nov 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow in the Tape Engine (tapeeng.exe) in CA (formerly Computer Associates) BrightStor ARCserve Backup 11.5 and earlier allows remote attackers to execute arbitrary code via certain RPC requests to TCP port 6502.

## Which versions are affected by CVE-2006-6076?

It affects 3 products.


Products: Broadcom Brightstor Arcserve Backup, Ca Brightstor Arcserve Backup, Ca Brightstor Arcserve Backup Agent.

## How do I fix CVE-2006-6076?

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

## Is CVE-2006-6076 being exploited?

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

Public exploit code:

- CA BrightStor ARCserve Tape Engine Buffer Overflow (metasploit)
- CA BrightStor ARCserve - Tape Engine Buffer Overflow (Metasploit) (exploitdb)
- CA BrightStor ARCserve Tape Engine 0x8A Buffer Overflow (metasploit)

## Other vulnerabilities in n/a

- [CVE-2008-3175](https://insights.sbomify.com/CVE-2008-3175/): Integer overflow in n/a (critical 10.0)
- [CVE-2008-2241](https://insights.sbomify.com/CVE-2008-2241/): Path traversal in n/a (critical 10.0)
- [CVE-2007-5325](https://insights.sbomify.com/CVE-2007-5325/): Memory corruption in n/a (critical 10.0)
- [CVE-2007-5326](https://insights.sbomify.com/CVE-2007-5326/): Memory corruption in n/a (critical 10.0)
- [CVE-2007-5327](https://insights.sbomify.com/CVE-2007-5327/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-6076 and fix it if it is affected.

What it is: CVE-2006-6076 is a critical memory corruption vulnerability in n/a, published on 24 Nov 2006. 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-2006-6076 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-2006-6076/ (Markdown: https://insights.sbomify.com/CVE-2006-6076/index.md)
```

## Sources

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

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