# CVE-2011-2407: Auth bypass in n/a

> Remote attackers can bypass authentication to gain unauthorized access to HP OpenView Performance Insight, potentially leading to privilege escalation and data exposure.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Aug 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-p8wc-fx77-5g4h

## What is CVE-2011-2407?

CVE-2011-2407 is a medium-severity authentication bypass vulnerability in n/a, published on 11 Aug 2011. It can be exploited over the network, with no action from the victim.

### Official description

Unspecified vulnerability in HP OpenView Performance Insight 5.3, 5.31, 5.4, 5.41, 5.41.001, and 5.41.002 allows remote attackers to obtain access via unknown vectors.

## Which versions are affected by CVE-2011-2407?

It affects 1 product.


Products: Hp Openview Performance Insight.

## How do I fix CVE-2011-2407?

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

## Is CVE-2011-2407 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-0276](https://insights.sbomify.com/CVE-2011-0276/): Hardcoded credentials in n/a (critical 10.0)
- [CVE-2010-0447](https://insights.sbomify.com/CVE-2010-0447/): Auth bypass in n/a (critical 10.0)
- [CVE-2011-2410](https://insights.sbomify.com/CVE-2011-2410/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2011-2406](https://insights.sbomify.com/CVE-2011-2406/): Cross-site scripting in n/a (low 3.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-2407 and fix it if it is affected.

What it is: CVE-2011-2407 is a medium-severity authentication bypass vulnerability in n/a, published on 11 Aug 2011. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-2407 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-2011-2407/ (Markdown: https://insights.sbomify.com/CVE-2011-2407/index.md)
```

## Sources

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

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