# CVE-2009-3099: Other in n/a

> Unspecified remote vulnerability in HP OpenView Operations Manager allows attackers to cause unknown impacts, requiring further investigation due to lack of details.

- **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 stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 8 Sep 2009
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-m5f4-ppqh-p8pq

## What is CVE-2009-3099?

CVE-2009-3099 is a critical vulnerability in n/a, published on 8 Sep 2009. It can be exploited over the network.

### Official description

Unspecified vulnerability in HP OpenView Operations Manager 8.1 on Windows Server 2003 SP2 allows remote attackers to have an unknown impact, related to a "Remote exploit," as demonstrated by a certain module in VulnDisco Pack Professional 8.11, a different vulnerability than CVE-2007-3872.  NOTE: as of 20090903, this disclosure has no actionable information. However, because the VulnDisco Pack author is a reliable researcher, the issue is being assigned a CVE identifier for tracking purposes.

## Which versions are affected by CVE-2009-3099?

It affects 1 product.


Products: Hp Operations Manager.

## How do I fix CVE-2009-3099?

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

## Is CVE-2009-3099 being exploited?

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

Public exploit code:

- HP Operations Manager - Default Manager 8.1 Account Remote Security (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2016-1985](https://insights.sbomify.com/CVE-2016-1985/): Deserialization in n/a (critical 10.0)
- [CVE-2014-2648](https://insights.sbomify.com/CVE-2014-2648/): Other in n/a (critical 10.0)
- [CVE-2009-4189](https://insights.sbomify.com/CVE-2009-4189/): Hardcoded credentials in n/a (critical 10.0)
- [CVE-2009-3843](https://insights.sbomify.com/CVE-2009-3843/): File upload in n/a (critical 10.0)
- [CVE-2016-4373](https://insights.sbomify.com/CVE-2016-4373/): Deserialization in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-3099 and fix it if it is affected.

What it is: CVE-2009-3099 is a critical vulnerability in n/a, published on 8 Sep 2009. It can be exploited over the network.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-3099 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-2009-3099/ (Markdown: https://insights.sbomify.com/CVE-2009-3099/index.md)
```

## Sources

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

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