# CVE-2017-14355: Privilege escalation in n/a

> Local attackers can exploit a vulnerability in HPE Connected Backup to escalate privileges on the affected system.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Dec 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-839q-87qf-rx5j

## What is CVE-2017-14355?

CVE-2017-14355 is a high-severity vulnerability in n/a, published on 5 Dec 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A potential security vulnerability has been identified in HPE Connected Backup versions 8.6 and 8.8.6. The vulnerability could be exploited locally to allow escalation of privilege.

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

It affects 1 product.


Products: Microfocus Connected Backup.

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

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

## Is CVE-2017-14355 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-14355 exists.

Public exploit code:

- HP Connected Backup 8.6/8.8.6 - Local Privilege Escalation (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-14355 is a high-severity vulnerability in n/a, published on 5 Dec 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-14355 exists.

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-2017-14355/ (Markdown: https://insights.sbomify.com/CVE-2017-14355/index.md)
```

## Sources

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

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