# CVE-2015-2109: Auth bypass in n/a

> Remote attackers can bypass authentication in HP Operations Orchestration to access or modify sensitive data without credentials.

- **Severity:** High 7.5 (`AV:N/AC:L/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:** 31 Mar 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-68rx-77gv-3q44

## What is CVE-2015-2109?

CVE-2015-2109 is a high-severity authentication bypass vulnerability in n/a, published on 31 Mar 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unspecified vulnerability in HP Operations Orchestration 10.x allows remote attackers to bypass authentication, and obtain sensitive information or modify data, via unknown vectors.

## Which versions are affected by CVE-2015-2109?

It affects 1 product.


Products: Hp Operations Orchestration.

## How do I fix CVE-2015-2109?

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

## Is CVE-2015-2109 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-3258](https://insights.sbomify.com/CVE-2012-3258/): Code injection in n/a (critical 10.0)
- [CVE-2016-8519](https://insights.sbomify.com/CVE-2016-8519/): Deserialization in Operations Orchestration (critical 9.8)
- [CVE-2017-8994](https://insights.sbomify.com/CVE-2017-8994/): Code injection in HPE Operations Orchestration (critical 9.8)
- [CVE-2016-1997](https://insights.sbomify.com/CVE-2016-1997/): Deserialization in n/a (critical 9.8)
- [CVE-2015-5451](https://insights.sbomify.com/CVE-2015-5451/): Cross-site request forgery in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-2109 and fix it if it is affected.

What it is: CVE-2015-2109 is a high-severity authentication bypass vulnerability in n/a, published on 31 Mar 2015. 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-2015-2109 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-2015-2109/ (Markdown: https://insights.sbomify.com/CVE-2015-2109/index.md)
```

## Sources

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

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