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

> Remote attackers can execute arbitrary code on HP TippingPoint SMS and vSMS systems by exploiting an unauthenticated JBoss RMI interface.

- **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:** 26 Apr 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-cg3p-9j97-f4w2

## What is CVE-2015-2117?

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

### Official description

HP TippingPoint Security Management System (SMS) and TippingPoint Virtual Security Management System (vSMS) before 4.1 patch 3 and 4.2 before patch 1 do not require authentication for JBoss RMI requests, which allows remote attackers to execute arbitrary code by (1) uploading this code within an archive or (2) instantiating a class.

Weakness: CWE-287 (Improper Authentication)

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

It affects 2 products.


Products: Hp Tippingpoint Security Management System, Hp Tippingpoint Virtual Security Management System.

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

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

## Is CVE-2015-2117 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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