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

> Remote attackers can execute arbitrary code via a stack-based buffer overflow in the BrightStor ARCserve Backup Agent for SQL Server.

- **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 needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Aug 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-rmpr-37mr-xqm2

## What is CVE-2005-1272?

CVE-2005-1272 is a high-severity memory corruption vulnerability in n/a, published on 5 Aug 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Stack-based buffer overflow in the Backup Agent for Microsoft SQL Server in BrightStor ARCserve Backup Agent for SQL Server 11.0 allows remote attackers to execute arbitrary code via a long string sent to port (1) 6070 or (2) 6050.

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

It affects 4 products.


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

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

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

## Is CVE-2005-1272 being exploited?

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

Public exploit code:

- CA BrightStor Agent for Microsoft SQL Overflow (metasploit)
- CA BrightStor ARCserve Backup Agent - 'dbasqlr.exe' Remote Overflow (exploitdb)
- CA BrightStor Agent for Microsoft SQL - Remote Overflow (Metasploit) (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-1272 and fix it if it is affected.

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

## Sources

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

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