dbcve.org
LoadrunnerApplication · Hp

CVE-2015-6857

HIGH · 7.2 CVSS v2.0 Published 2015-11-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
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
Unspecified vulnerability in Virtual Table Server (VTS) in HP LoadRunner 11.52, 12.00, 12.01, 12.02, and 12.50 allows remote attackers to execute arbitrary code via unknown vectors, aka ZDI-CAN-3138.

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 confidence

HP LoadRunner Virtual Table Server (VTS) contains an unspecified vulnerability allowing remote unauthenticated attackers to execute arbitrary code. The VTS component exposes network services that lack proper input validation or access controls, enabling remote code execution without any authentication credentials. This affects LoadRunner versions 11.52 through 12.50.

MitigationApply HP patches as they become available. If patches are unavailable, restrict network access to VTS ports via firewall rules or disable the VTS component if not required for testing operations.

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
Local
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:L/AC:L/Au:N/C:C/I:C/A:C

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. Identify if HP LoadRunner or Performance Center is installed
    Check for installation directories such as C:\Program Files\HP\LoadRunner or C:\HP\Performance Center on Windows, or /opt/hp/LoadRunner on Linux. Also check Add/Remove Programs or system inventory tools for HP LoadRunner or HP Performance Center.
    Affected if HP LoadRunner or HP Performance Center software is found on the system.
  2. Determine the installed version of LoadRunner or Performance Center
    Locate the version information in the installation directory, typically in a version.txt or about dialog, or check the registry key HKEY_LOCAL_MACHINE\SOFTWARE\HP\LoadRunner\Version on Windows. Compare the installed version to the affected versions: 11.52, 12.00, 12.01, 12.02, 12.50 for LoadRunner and 11.52, 12.00, 12.01, 12.20, 12.50 for Performance Center.
    Affected if The installed version matches exactly one of the affected versions listed in the CVE.
  3. Check if the Virtual Table Server (VTS) component is running
    Look for the VTS executable (vts.exe or vts) in the LoadRunner installation directory, typically under bin or vts folder. Use Task Manager or command 'tasklist | findstr vts' on Windows, or 'ps aux | grep vts' on Linux to check if VTS process is active.
    Affected if The VTS executable is running as a process on the system.
  4. Identify open network ports associated with VTS
    Run 'netstat -an | findstr 8888' or use a port scanner to check for listening ports in the 8888-8890 range which are default VTS ports. Check the VTS configuration file (vts.cfg or vts.ini) in the vts\config folder for the configured port.
    Affected if VTS is listening on any network port and accepting remote connections.
  5. Verify network accessibility of VTS ports
    Use 'telnet <localhost> <port>' or 'Test-NetConnection -Port <port>' from external hosts to confirm VTS ports are reachable from network. Check firewall rules with 'netsh firewall show all' on Windows or iptables -L on Linux.
    Affected if VTS ports are accessible from network hosts without authentication requirements.

A system is affected if it runs HP LoadRunner version 11.52, 12.00, 12.01, 12.02, or 12.50 (or HP Performance Center 11.52, 12.00, 12.01, 12.20, or 12.50) with the VTS component actively running and exposing network services to unauthenticated remote access.

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 HP patches as they become available. If patches are unavailable, restrict network access to VTS ports via firewall rules or disable the VTS component if not required for testing operations.

Fix this in Loadrunner Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-6857 — 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-2015-6857 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