# CVE-2005-2051: Memory corruption in n/a

> Remote attackers can execute arbitrary code via a buffer overflow in the VERITAS Backup Exec Web Administration Console.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jun 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-48m4-p7hc-9m25

## What is CVE-2005-2051?

CVE-2005-2051 is a high-severity memory corruption vulnerability in n/a, published on 26 Jun 2005. It can be exploited over the network, with no action from the victim.

### Official description

Buffer overflow in the VERITAS Backup Exec Web Administration Console (BEWAC) 9.0 4367 through 10.0 rev. 5484 allows remote attackers to execute arbitrary code.

## Which versions are affected by CVE-2005-2051?

It affects 1 product.


Products: Symantec Veritas Backup Exec.

## How do I fix CVE-2005-2051?

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

## Is CVE-2005-2051 being exploited?

There is no known exploitation of CVE-2005-2051 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-2005-2051 and fix it if it is affected.

What it is: CVE-2005-2051 is a high-severity memory corruption vulnerability in n/a, published on 26 Jun 2005. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-2051 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-2005-2051/ (Markdown: https://insights.sbomify.com/CVE-2005-2051/index.md)
```

## Sources

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

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