# CVE-2014-2614: Auth bypass in n/a

> Remote attackers can bypass authentication in HP SiteScope, gaining unauthorized access to the monitoring system.

- **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:** 7 Jul 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-mcv8-6886-g6ph

## What is CVE-2014-2614?

CVE-2014-2614 is a high-severity authentication bypass vulnerability in n/a, published on 7 Jul 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unspecified vulnerability in HP SiteScope 11.1x through 11.13 and 11.2x through 11.24 allows remote attackers to bypass authentication via unknown vectors, aka ZDI-CAN-2140.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2014-2614?

It affects 1 product.


Products: Hp Sitescope.

## How do I fix CVE-2014-2614?

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

## Is CVE-2014-2614 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-2367](https://insights.sbomify.com/CVE-2013-2367/): Code injection in n/a (critical 10.0)
- [CVE-2012-3259](https://insights.sbomify.com/CVE-2012-3259/): Code injection in n/a (critical 10.0)
- [CVE-2012-3260](https://insights.sbomify.com/CVE-2012-3260/): Code injection in n/a (critical 10.0)
- [CVE-2012-3261](https://insights.sbomify.com/CVE-2012-3261/): Code injection in n/a (critical 10.0)
- [CVE-2012-3262](https://insights.sbomify.com/CVE-2012-3262/): Code injection in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-2614 and fix it if it is affected.

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

## Sources

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

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