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

> Remote attackers can cause denial of service or execute arbitrary code via crafted RPC messages in Symantec Backup Exec Remote Agents.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/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:** 14 Aug 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-cm8p-r3h5-8h2x

## What is CVE-2006-4128?

CVE-2006-4128 is a medium-severity memory corruption vulnerability in n/a, published on 14 Aug 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple heap-based buffer overflows in Symantec VERITAS Backup Exec for Netware Server Remote Agent for Windows Server 9.1 and 9.2 (all builds), Backup Exec Continuous Protection Server Remote Agent for Windows Server 10.1 (builds 10.1.325.6301, 10.1.326.1401, 10.1.326.2501, 10.1.326.3301, and 10.1.327.401), and Backup Exec for Windows Server and Remote Agent 9.1 (build 9.1.4691), 10.0 (builds 10.0.5484 and 10.0.5520), and 10.1 (build 10.1.5629) allow remote attackers to cause a denial of service (application crash) and possibly execute arbitrary code via a crafted RPC message.

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

It affects 1 product.


Products: Symantec Veritas Backup Exec.

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

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

## Is CVE-2006-4128 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-2611](https://insights.sbomify.com/CVE-2005-2611/): Hardcoded credentials in n/a (critical 10.0)
- [CVE-2005-0771](https://insights.sbomify.com/CVE-2005-0771/): Missing authorization in n/a (critical 10.0)
- [CVE-2004-1172](https://insights.sbomify.com/CVE-2004-1172/): Memory corruption in n/a (critical 10.0)
- [CVE-2005-0773](https://insights.sbomify.com/CVE-2005-0773/): Memory corruption in n/a (high 7.5)
- [CVE-2005-2079](https://insights.sbomify.com/CVE-2005-2079/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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