CVE-2017-5813
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 unauthenticated access vulnerability 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 confidenceRemote unauthenticated access vulnerability in HPE Network Automation allows an attacker to gain access to the network management system without valid credentials. This affects versions 9.1x through 10.2x.
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
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L
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 HPE Network Automation installationLocate the HPE Network Automation installation directory, typically under /opt/hp/hpna or C:\hp\hpnna on Windows. Check for the presence of core application files such as nmserver, na, or hpna in the installation path.Affected if HPE Network Automation software is not found on the system, the vulnerability does not apply.
-
Identify installed versionAccess the HPE Network Automation web interface and navigate to Help > About, or check the version.txt or version.info file in the installation directory. Alternatively, run the command 'nmsetcd -v' or check the output of 'nmserver -version' from the installation bin folder.Affected if The installed version matches any of: 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, or falls within the 9.1x to 10.2x range.
-
Verify management interface accessibilityCheck network configuration files or firewall rules to determine if the HPE Network Automation management ports (typically TCP 80, 443, or 8080) are exposed to untrusted networks or the public internet. Review network interfaces and routing tables.Affected if The management interface is reachable from untrusted networks without proper network segmentation or access controls.
-
Check for unauthorized access indicatorsReview HPE Network Automation audit logs, access logs, and authentication logs for failed login attempts from unknown IP addresses, successful logins without corresponding credentials, or unusual API access patterns. Logs are typically located in the /logs or /audit directory under the installation path.
You are affected if HPE Network Automation is installed and the version falls between 9.1x and 10.2x inclusive, and the management interface is accessible from a network where untrusted actors could reach it.
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 dataUpgrade HPE Network Automation to a version beyond 10.2x that includes the security patch. If immediate patching is not possible, restrict network access to the management interface using firewall rules or VLAN isolation.
- Consultation4.0 h
- Implementation8.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5813 — 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-5813 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