CVE-2017-5803
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 Disclosure of Information vulnerability in HPE NonStop Servers using SSH Service version L series: T0801L02 through T0801L02^ABX; J and H series: T0801H01 through T0801H01^ACA was 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 Disclosure of Information vulnerability exists in HPE NonStop Servers running SSH Service. The vulnerability affects specific version ranges of the SSH service on L series (T0801L02 through T0801L02^ABX) and J/H series (T0801H01 through T0801H01^ACA) NonStop systems, potentially allowing unauthorized disclosure of sensitive system information via the SSH protocol.
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>= t0801h01, <= t0801h01\^aca>= t0801l02, <= t0801l02\^abxCVSS 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
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 NonStop systemRun 'uname -a' or 'nodeinfo' command in the OSS shell to verify the operating system is HPE NonStopAffected if System is not HPE NonStop - not applicable
-
Check NonStop OSS versionRun the 'version' command or inspect /etc/hpws_version to obtain the OSS version numberAffected if Version is within t0801h01 through t0801h01^aca (H/J series) OR t0801l02 through t0801l02^abx (L series)
-
Verify SSH service is enabledRun 'ps -ef | grep ssh' or check Pathway process list to confirm the SSH daemon (sshd) is runningAffected if SSH service is not present or not running - vulnerability cannot be triggered
-
Confirm SSH service versionRun 'ssh -V' or check the SSH daemon binary version to identify the SSH implementation versionAffected if SSH version corresponds to the affected NonStop OSS version ranges listed above
A system is affected if it is an HPE NonStop server with OSS version in the ranges t0801h01 to t0801h01^aca or t0801l02 to t0801l02^abx, and the SSH service is enabled and running.
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 appropriate HPE patch to update the SSH Service to a fixed version beyond the affected ranges. If patches are unavailable, restrict SSH access via network controls and monitor for unauthorized information disclosure attempts.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.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 $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5803 — 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-5803 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