# CVE-2007-3825: Memory corruption in n/a

> Remote attackers can execute arbitrary code via stack-based buffer overflows in the RPC implementation of CA Alert Notification Server.

- **Severity:** Critical 9.3 (`AV:N/AC:M/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:** 18 Jul 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-hqgm-p47x-vmfg

## What is CVE-2007-3825?

CVE-2007-3825 is a critical memory corruption vulnerability in n/a, published on 18 Jul 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple stack-based buffer overflows in the RPC implementation in alert.exe before 8.0.255.0 in CA (formerly Computer Associates) Alert Notification Server, as used in Threat Manager for the Enterprise, Protection Suites, certain BrightStor ARCserve products, and BrightStor Enterprise Backup, allow remote attackers to execute arbitrary code by sending certain data to unspecified RPC procedures.

## Which versions are affected by CVE-2007-3825?

It affects 8 products.


Products: Broadcom Alert Notification Server, Broadcom Brightstor Arcserve Backup, Broadcom Brightstor Enterprise Backup, Ca Anti-Virus for the Enterprise, Ca Brightstor Arcserve Backup, Ca Brightstor Arcserve Client, Ca Protection Suites, Ca Threat Manager.

## How do I fix CVE-2007-3825?

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

## Is CVE-2007-3825 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-3825 and fix it if it is affected.

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

## Sources

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

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