CVE-2017-5814
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 remote sql injection authentication bypass in HPE Network Automation version 9.1x, 9.2x, 10.0x, 10.1x and 10.2x were found.
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 confidenceA remote SQL injection vulnerability in HPE Network Automation allows unauthenticated attackers to bypass authentication by injecting malicious SQL queries into login parameters. This affects versions 9.1x through 10.2x and can be exploited remotely without valid credentials.
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.10= 9.20= 9.22= 9.22.01= 9.22.02= 10.00= 10.00.01= 10.00.02= 10.10= 10.11= 10.21CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/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 HPE Network Automation installationLocate the HPE Network Automation web interface or application binaries on the system. Check for the product by reviewing running services or installed applications that match the HPE Network Automation name.Affected if HPE Network Automation is installed and running on the system
-
Determine the installed versionAccess the HPE Network Automation admin interface or check the product's about/version page. Compare the installed version number against the affected list: 9.10, 9.20, 9.22, 9.22.01, 9.22.02, 10.00, 10.00.01, 10.00.02, 10.10, 10.11, 10.21.Affected if The installed version matches any of the versions listed in the affected products list
-
Verify login interface exposureDetermine if the HPE Network Automation login page is accessible from network locations that should not have access, such as the public internet or untrusted internal segments.Affected if The login interface is exposed to untrusted networks without proper access controls
-
Inspect logs for SQL injection patternsReview HPE Network Automation server logs, particularly authentication and access logs, for unusual SQL syntax or database error messages in login parameter fields.Affected if Logs contain SQL injection attempts or database errors in login-related fields
A system is affected if HPE Network Automation is installed with a version matching 9.10 through 10.21 and the login interface is accessible to potential attackers.
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 HPE security patch for CVE-2017-5814. If no patch is available, restrict network access to HPE Network Automation management interfaces and implement WAF rules to detect and block SQL injection attempts.
- Consultation4.0 h
- Implementation16.0 h
- Testing12.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 $9,920.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5814 — 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-5814 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