dbcve.org
LoadrunnerApplication · Hp

CVE-2013-6213

HIGH · 10.0 CVSS v2.0 Published 2014-04-19
Fix available
A fix is available. Upgrade to after 11.52 or later.
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
Unspecified vulnerability in Virtual User Generator in HP LoadRunner before 11.52 Patch 1 allows remote attackers to execute arbitrary code via unknown vectors, aka ZDI-CAN-1833.

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

Virtual User Generator (VuGen) in HP LoadRunner before version 11.52 Patch 1 contains an unspecified vulnerability allowing remote attackers to execute arbitrary code. The CVSS 10 score indicates trivial exploitability with complete impact on confidentiality, integrity, and availability. This is a critical remote code execution flaw in a load testing tool that processes user-created scripts and simulations.

MitigationApply HP LoadRunner 11.52 Patch 1 or later to address the vulnerability. As an immediate compensating control, restrict network access to LoadRunner components and consider isolating the VuGen environment from untrusted networks until the patch is applied.

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= 11.0.0.0= 11.50= 11.51

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

AV:N/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 installed HP LoadRunner version
    Open HP LoadRunner or VuGen, go to Help > About, or check the installed programs list in Windows Control Panel to find the exact version number
    Affected if The installed version is 11.0.0.0, 11.50, 11.51, or any version up to and including 11.52
  2. Confirm VuGen component is present
    Verify that Virtual User Generator (VuGen) is installed by checking for its executable (vugen.exe) in the LoadRunner bin directory, typically at C:\Program Files\HP\LoadRunner\bin\vugen.exe
    Affected if VuGen is installed and present on the system
  3. Check if VuGen service is running or accessible
    Open Windows Services console (services.msc) and look for HP LoadRunner services, or check if the VuGen listener port is open by running 'netstat -an | findstr 54345' (default VuGen port)
    Affected if VuGen service is running or its network port is listening
  4. Verify network exposure of LoadRunner components
    Run 'netstat -an' to list all listening ports and check if LoadRunner/VuGen ports are exposed to untrusted networks, or review firewall rules for any inbound rules allowing traffic to LoadRunner ports
    Affected if LoadRunner/VuGen ports are accessible from network segments that are not trusted or are externally exposed

You are affected if HP LoadRunner with VuGen is installed at version 11.0.0.0, 11.50, 11.51, or any version through 11.52, and the VuGen component is present and accessible on the network.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 11.52
Interim mitigation

Apply HP LoadRunner 11.52 Patch 1 or later to address the vulnerability. As an immediate compensating control, restrict network access to LoadRunner components and consider isolating the VuGen environment from untrusted networks until the patch is applied.

Recommended fix High confidence

HP LoadRunner 11.52 Patch 1 or later

  1. 1. Navigate to the HP Software Support website at h20564.www2.hp.com
  2. 2. Search for LoadRunner 11.52 Patch 1 or the latest available patch for your LoadRunner version
  3. 3. Download the patch file for HP LoadRunner 11.52 Patch 1
  4. 4. Back up your current LoadRunner installation and configuration
  5. 5. Apply the patch following the HP patch installation instructions
  6. 6. Verify the Virtual User Generator component is updated to the patched version
  7. 7. Test that Virtual User Generator functions normally after the patch

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Loadrunner Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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