CVE-2017-8195
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 · uneditedThe FusionSphere OpenStack V100R006C00SPC102(NFV) has an improper authentication vulnerability. Due to improper authentication on one port, an authenticated, remote attacker may exploit the vulnerability to execute more operations by send a crafted rest message.
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 confidenceFusionSphere OpenStack V100R006C00SPC102 has an improper authentication vulnerability on a specific port. An authenticated remote attacker can send crafted REST API messages to exploit the weak authentication, potentially escalating privileges or gaining unauthorized access to additional operations.
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= v100r006c00spc102\(nfv\)CVSS 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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/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.
-
Identify FusionSphere OpenStack versionRun 'vmware -l' or check the system management interface for the installed version. Alternatively, inspect the release manifest or about page in the FusionSphere management console.Affected if The installed version is exactly V100R006C00SPC102 (nfv build).
-
Locate the REST API service portCheck running services and listening ports on the FusionSphere management nodes using 'netstat -tulpn | grep -i rest' or review the service configuration files for the REST API endpoint.Affected if The REST API service is listening on any port and is network-accessible.
-
Verify REST API network exposureConfirm whether the REST API port is bound to a public or routable IP address rather than localhost only. Use 'ss -tulpn' or check the service bind address in the configuration.Affected if The REST API is bound to a non-localhost interface and accessible from network segments beyond the management network.
-
Inspect API authentication configurationReview the REST API configuration files and authentication settings. Check whether weak authentication methods or default credentials are enabled for the API endpoint.Affected if Weak authentication mechanisms, fallback to legacy auth, or unauthenticated endpoints are found in the API configuration.
A user is affected if they are running exactly version V100R006C00SPC102 with the REST API exposed to network and using the vulnerable authentication configuration.
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.
From vendor dataApply vendor-supplied patches for V100R006C00SPC102. If patching is delayed, restrict network access to the vulnerable port and implement additional authentication controls on the affected REST API endpoint.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-8195 — 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-8195 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