CVE-2017-13984
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 delete arbitrary files via servlet directory traversal.
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 authenticated users to delete arbitrary files on the server through a directory traversal vulnerability in the servlet 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= 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 BSM Platform installation directory and identify the Application Performance Management System Health component. Common paths may include /opt/HP/BSM or similar. Check for the presence of the APM System Health web application files.Affected if HPE BSM Platform Application Performance Management System Health is present on the server
-
Identify the installed versionCheck the version of the Application Performance Management System Health component. Look for version files in the installation directory, or access the web interface and check the about/help section for the version number.Affected if The installed version is exactly 9.26, 9.30, or 9.40
-
Verify servlet component accessibilityCheck if the servlet component is exposed via the web interface. Look for endpoints under the BSM console that handle file operations or system health queries. Review the web server configuration to confirm the servlet is accessible.Affected if The servlet component is accessible via the BSM web interface without additional access restrictions
-
Review access logs for directory traversal patternsExamine the BSM Platform access and audit logs for suspicious requests containing traversal sequences such as ../ or ..\ in the URL parameters. Focus on requests to servlet endpoints that could indicate file deletion attempts.Affected if Logs show authenticated requests with directory traversal patterns targeting arbitrary file paths
A system is affected if it runs HPE BSM Platform Application Performance Management System Health version 9.26, 9.30, or 9.40 with the servlet component accessible to authenticated 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-supplied patch for this vulnerability. If no patch is immediately available, restrict network access to the BSM platform to trusted users only and implement file system access monitoring to detect unauthorized deletion attempts.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-13984 — 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-13984 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