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

> Remote attackers can execute arbitrary code via a stack-based buffer overflow in the HP OpenView Storage Data Protector backup client service.

- **Severity:** Critical 10.0 (`AV:N/AC:L/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 Dec 2009
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-98xx-c784-66x3

## What is CVE-2007-2280?

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

### Official description

Stack-based buffer overflow in OmniInet.exe (aka the backup client service daemon) in the Application Recovery Manager component in HP OpenView Storage Data Protector 5.50 and 6.0 allows remote attackers to execute arbitrary code via an MSG_PROTOCOL command with long arguments, a different vulnerability than CVE-2009-3844.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Hp Openview Storage Data Protector.

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

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

## Is CVE-2007-2280 being exploited?

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

Public exploit code:

- HP OmniInet.exe MSG_PROTOCOL Buffer Overflow (metasploit)
- HP - 'OmniInet.exe' MSG_PROTOCOL Buffer Overflow (Metasploit) (2) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2011-1865](https://insights.sbomify.com/CVE-2011-1865/): Memory corruption in n/a (critical 10.0)
- [CVE-2011-1866](https://insights.sbomify.com/CVE-2011-1866/): Memory corruption in n/a (critical 10.0)
- [CVE-2011-1728](https://insights.sbomify.com/CVE-2011-1728/): Memory corruption in n/a (critical 10.0)
- [CVE-2011-1729](https://insights.sbomify.com/CVE-2011-1729/): Memory corruption in n/a (critical 10.0)
- [CVE-2011-1730](https://insights.sbomify.com/CVE-2011-1730/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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