CVE-2017-13985
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 · uneditedAn authentication vulnerability in HPE BSM Platform Application Performance Management System Health product versions 9.26, 9.30 and 9.40, allows remote users to traverse directory leading to disclosure of information.
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 confidenceAn authentication vulnerability in HPE BSM Platform Application Performance Management System Health versions 9.26, 9.30, and 9.40 allows remote users to bypass authentication and traverse directories, leading to unauthorized disclosure of sensitive information.
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.26= 9.30= 9.40CVSS 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
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/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 BSM Platform is installedLocate the HPE BSM Platform Application Performance Management System Health installation on your system or check your software inventory for this productAffected if The product is present on the system
-
Identify the installed versionCheck the installed version of HPE BSM Platform Application Performance Management System Health using the product's built-in version check, about page, or installation directory metadataAffected if The installed version is exactly 9.26, 9.30, or 9.40
-
Verify the web interface is accessibleDetermine if the BSM web portal or application interface is network-accessible (check if port 8080, 8443, or the configured HTTP/HTTPS ports are listening and reachable)Affected if The web interface is exposed and reachable
-
Test for unauthenticated directory traversalSend a crafted HTTP request with directory traversal sequences (such as ../../) to the web interface endpoints without providing valid authentication credentialsAffected if The server returns sensitive files or directory contents without requiring authentication
-
Check for sensitive file exposureAttempt to access known sensitive paths such as configuration files, logs, or system directories through the web interface using traversal patternsAffected if Sensitive files or directories are accessible without authentication
You are affected if HPE BSM Platform Application Performance Management System Health versions 9.26, 9.30, or 9.40 is installed and its web interface is accessible, allowing unauthenticated directory traversal to sensitive files.
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-supplied patch for this vulnerability. If no patch is available, implement web application firewall rules to block directory traversal patterns and ensure proper input validation on all user-supplied path parameters.
- Consultation4.0 h
- Implementation4.0 h
- Testing8.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,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-13985 — 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-13985 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