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

> Local attackers can exploit inventory gathering components in FlexNet Manager Suite to gain elevated privileges on the system.

- **Severity:** High 7.8 (`CVSS:3.1/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:** 29 Mar 2023
- **Updated:** 18 Feb 2025
- **Also known as:** GHSA-frrc-f75h-9j62

## What is CVE-2017-6894?

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

### Official description

A vulnerability exists in FlexNet Manager Suite releases 2015 R2 SP3 and earlier (including FlexNet Manager Platform 9.2 and earlier) that affects the inventory gathering components and can be exploited by local users to perform certain actions with elevated privileges on the local system.

Weakness: CWE-269 (Improper Privilege Management)

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

It affects 2 products.


Products: Flexera Flexnet Manager, Flexera Flexnet Manager Suite 2015.

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

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

## Is CVE-2017-6894 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-6894 is a high-severity vulnerability in n/a, published on 29 Mar 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-6894 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-2017-6894/ (Markdown: https://insights.sbomify.com/CVE-2017-6894/index.md)
```

## Sources

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

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