dbcve.org
LoadrunnerApplication · Hp

CVE-2016-4360

CRITICAL · 9.1 CVSS v3.0 Published 2016-06-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
web/admin/data.js in the Performance Center Virtual Table Server (VTS) component in HPE LoadRunner 11.52 through patch 3, 12.00 through patch 1, 12.01 through patch 3, 12.02 through patch 2, and 12.50 through patch 3 and Performance Center 11.52 through patch 3, 12.00 through patch 1, 12.01 through patch 3, 12.20 through patch 2, and 12.50 through patch 1 do not restrict file paths sent to an unlink call, which allows remote attackers to delete arbitrary files via the path parameter to data/import_csv, aka ZDI-CAN-3555.

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 · high confidence

A path traversal vulnerability in the Virtual Table Server (VTS) component of HPE LoadRunner and Performance Center allows remote attackers to delete arbitrary files. The data.js file in the web/admin/ directory fails to validate the path parameter before passing it to an unlink() call in the data/import_csv endpoint, enabling directory traversal sequences (e.g., ../../../etc/passwd) to target any file the web server process can delete.

MitigationApply the vendor patches for the affected LoadRunner and Performance Center versions. If immediate patching is not possible, restrict network access to the VTS component or disable it if not required.

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
LoadrunnerApplication
Affected:= 11.52= 12.00= 12.01= 12.02= 12.50
Performance CenterApplication
Affected:= 11.52= 12.00= 12.01= 12.20= 12.50

CVSS 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
None
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if Virtual Table Server (VTS) is installed
    On Windows, check for VTS installation directory (typically C:\Program Files\HP\LoadRunner\bin\VTS or C:\HP\LoadRunner\bin\VTS). On Linux, check /opt/HP/LoadRunner/bin/VTS or similar paths. Look for the vts.exe or vts service.
    Affected if VTS component is present on the system
  2. Determine installed LoadRunner or Performance Center version
    Check the installed version via the LoadRunner or Performance Center installer, or check the product version in Add/Remove Programs (Windows) or via registry under HKLM\SOFTWARE\HP\LoadRunner or HKLM\SOFTWARE\HP\Performance Center.
    Affected if Version matches 11.52, 12.00, 12.01, 12.02, or 12.50 for LoadRunner; or 11.52, 12.00, 12.01, 12.20, or 12.50 for Performance Center
  3. Verify VTS web interface is accessible
    If VTS is running, attempt to access http://localhost:8080/web/admin/data.js or http://[VTS_host]:8080/web/admin/ to confirm the vulnerable web/admin/ directory exists and is reachable.
    Affected if The web/admin/ directory and data.js file are accessible via the VTS web port (default 8080)
  4. Check network exposure of VTS service
    Run netstat -an | findstr 8080 or similar to see if VTS is listening on 0.0.0.0:8080 or on interfaces accessible from untrusted networks, rather than only on localhost or restricted internal interfaces.
    Affected if VTS port 8080 is listening on all interfaces (0.0.0.0) or is accessible from untrusted network segments

A defender is affected if VTS is installed, the LoadRunner or Performance Center version matches the affected list, and the VTS web interface (port 8080) is accessible to potentially malicious users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patches for the affected LoadRunner and Performance Center versions. If immediate patching is not possible, restrict network access to the VTS component or disable it if not required.

Fix this in Loadrunner Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-4360 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-4360 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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