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

> Remote attackers can execute arbitrary code on HP Executive Scorecard via the unauthenticated Java Glassfish Admin Console.

- **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:** 19 Jun 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-h932-r8mq-2ccg

## What is CVE-2014-2609?

CVE-2014-2609 is a critical authentication bypass vulnerability in n/a, published on 19 Jun 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Java Glassfish Admin Console in HP Executive Scorecard 9.40 and 9.41 does not require authentication, which allows remote attackers to execute arbitrary code via a session on TCP port 10001, aka ZDI-CAN-2116.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Hp Executive Scorecard.

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

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

## Is CVE-2014-2609 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-2611](https://insights.sbomify.com/CVE-2014-2611/): Path traversal in n/a (critical 9.0)
- [CVE-2014-2610](https://insights.sbomify.com/CVE-2014-2610/): Path traversal in n/a (high 7.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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