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

> Remote attackers can execute arbitrary code via crafted requests to the HP OpenView Operations Shared Trace Service due to stack-based buffer overflows.

- **Severity:** Medium 6.8 (`AV:N/AC:M/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:** 9 Aug 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-7hp2-wg9m-cm55

## What is CVE-2007-3872?

CVE-2007-3872 is a medium-severity memory corruption vulnerability in n/a, published on 9 Aug 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 Shared Trace Service (OVTrace) service for HP OpenView Operations A.07.50 for Windows, and possibly earlier versions, allow remote attackers to execute arbitrary code via certain crafted requests.

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

It affects 2 products.


Products: Hp Openview Operations, Hp Shared Trace Service.

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

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

## Is CVE-2007-3872 being exploited?

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

Public exploit code:

- HP OpenView Operations OVTrace Buffer Overflow (metasploit)
- HP OpenView - Operations OVTrace Buffer Overflow (Metasploit) (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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