# CVE-2017-14350: Auth bypass in HPE Application Performance Management (APM)

> Remote attackers can execute arbitrary code on HPE APM Platform due to missing authentication for critical functions.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Sep 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-mr2j-x367-gmvc

## What is CVE-2017-14350?

CVE-2017-14350 is a critical authentication bypass vulnerability in Micro Focus HPE Application Performance Management (APM), published on 29 Sep 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A potential security vulnerability has been identified in HPE Application Performance Management (BSM) Platform versions 9.26, 9.30, 9.40. The vulnerability could be remotely exploited to allow code execution.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2017-14350?

It affects 1 product.


Products: Hp Application Performance Management.

## How do I fix CVE-2017-14350?

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

## Is CVE-2017-14350 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-14350 and fix it if it is affected.

What it is: CVE-2017-14350 is a critical authentication bypass vulnerability in Micro Focus HPE Application Performance Management (APM), published on 29 Sep 2017. 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-2017-14350 in the wild and no public exploit code.

Affected product: Micro Focus HPE Application Performance Management (APM). 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-2017-14350/ (Markdown: https://insights.sbomify.com/CVE-2017-14350/index.md)
```

## Sources

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

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