CVE-2017-6894
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceLocal privilege escalation vulnerability in FlexNet Manager Suite inventory gathering components (versions 2015 R2 SP3 and earlier, including FlexNet Manager Platform 9.2 and earlier) allows unprivileged local users to execute code or commands with elevated SYSTEM-level privileges on the affected system.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 9.2all versions= r2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if FlexNet Manager Suite or FlexNet Manager Platform is installedOn Windows, open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Flexera Software\FlexNet Manager Suite or HKEY_LOCAL_MACHINE\SOFTWARE\Flexera Software\FlexNet Manager Platform. Alternatively, check Program Files for a Flexera folder.Affected if Either registry key exists or the Flexera folder is present in Program Files, indicating the product is installed.
-
Identify the installed version of FlexNet ManagerIn the Windows Registry, check the Version value under the FlexNet Manager Suite or FlexNet Manager Platform registry key. If using the administrative console, view the About or System Information page.Affected if The version displayed is 9.2 or lower, or the build corresponds to 2015 R2 SP3 or earlier.
-
Locate inventory gathering componentsLook for the 'FlexNet Manager Data Gathering' or 'FlexNet Inventory Manager' service in Windows Services console (services.msc). Also check for installation directories containing 'Inventory' or 'Data Gathering' in the FlexNet installation path.Affected if The inventory gathering service is present and installed on the system.
-
Verify service account for inventory componentsOpen Services console, find the FlexNet inventory or data gathering service, right-click and select Properties. Check the 'Log on as' account configuration.Affected if The service runs under SYSTEM, Local System, or an administrative account, and unprivileged users have write access to the service executable path.
If FlexNet Manager Suite or FlexNet Manager Platform is installed with version 9.2 or earlier (or any 2015 version), and the inventory gathering component is present and runs with elevated privileges, the environment is affected by this privilege escalation vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade FlexNet Manager Suite to a version newer than 2015 R2 SP3 / 9.2, or apply vendor-supplied patches if available for these legacy versions.
FlexNet Manager Suite 2015 R2 SP4 or later / FlexNet Manager Platform 9.2 SP1 or 9.3 or newer
- 1. Identify the current installed version of FlexNet Manager Suite or FlexNet Manager Platform by checking the product's 'About' or version information.
- 2. If running FlexNet Manager Suite 2015 R2 SP3 or earlier, plan an upgrade to FlexNet Manager Suite 2015 R2 SP4 or later (or the latest supported release).
- 3. If running FlexNet Manager Platform 9.2 or earlier, plan an upgrade to version 9.2 SP1, 9.3, or the latest available release.
- 4. Review the Flexera Community (community.flexera.com) for the specific patch or hotfix release notes related to CVE-2017-6894.
- 5. Test the upgrade in a non-production environment to verify compatibility with existing systems and integrations.
- 6. Schedule maintenance window and perform the upgrade following Flexera's official installation documentation.
- 7. After upgrade, verify the inventory gathering components are functioning correctly and the vulnerability is resolved.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-6894 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-6894 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data