CVE-2017-2714
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 GaussDB in FusionSphere OpenStack V100R005C10SPC705 and earlier versions has a buffer overflow vulnerability. An authenticated attacker on the LAN can exploit this vulnerability to execute arbitrary code or cause a denial of service (DoS) condition in the affected 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 confidenceGaussDB in Huawei FusionSphere OpenStack V100R005C10SPC705 and earlier versions contains a buffer overflow vulnerability. An authenticated attacker with LAN access can exploit this to execute arbitrary code or cause denial of service. The vulnerability stems from improper bounds checking in the database component.
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<= v100r005c10spc705CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:A/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.
-
Confirm GaussDB component is presentIdentify if GaussDB database component is installed as part of the FusionSphere OpenStack environment. This may be listed in system inventory, component listings, or database server configurations.Affected if GaussDB is installed as part of FusionSphere OpenStack
-
Determine FusionSphere OpenStack versionLocate the installed FusionSphere OpenStack version through system information, version check command, or management interface. Common methods include checking the OpenStack horizon dashboard, using openstack CLI commands, or reviewing system documentation.Affected if Version cannot be determined or is <= V100R005C10SPC705
-
Compare version against affected rangeCompare the installed version number to the affected range: V100R005C10SPC705 and earlier versions. If the version is at or below this release, the vulnerability is present.Affected if Version is V100R005C10SPC705 or any earlier version (e.g., V100R005C10SPC600, V100R005C10SPC500, etc.)
-
Verify network accessibility of database componentCheck if the GaussDB component is accessible over the LAN. Review firewall rules, network ACLs, and database listening interfaces. The vulnerability requires network access to exploit.Affected if GaussDB is exposed to unauthenticated or untrusted LAN access
The environment is affected if GaussDB is installed and the FusionSphere OpenStack version is V100R005C10SPC705 or earlier, especially if the database is accessible over the network to untrusted users.
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 the vendor patch or upgrade GaussDB to a version beyond V100R005C10SPC705. If patches are unavailable, restrict LAN access to trusted personnel and monitor for exploitation attempts.
- Consultation8.0 h
- Implementation16.0 h
- Testing24.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,232.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-2714 — 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-2714 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