CVE-2013-2369
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 · uneditedUnspecified vulnerability in HP LoadRunner before 11.52 allows remote attackers to execute arbitrary code via unknown vectors, aka ZDI-CAN-1670.
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 confidenceHP LoadRunner before version 11.52 contains an unspecified vulnerability allowing remote attackers to execute arbitrary code via unknown vectors (ZDI-CAN-1670). The CVSS 7.5 score indicates high-severity remote code execution capability.
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<= 11.51= 9.0.0= 9.50.0= 9.51= 9.52= 11.0.0.0= 11.50CVSS 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
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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.
-
Check LoadRunner version via Windows RegistryOpen regedit and navigate to HKLM\SOFTWARE\Mercury Interactive\LoadRunner\ or HKLM\SOFTWARE\Hewlett-Packard\LoadRunner\ and look for a Version or ProductVersion string valueAffected if The displayed version matches any of these: 9.0.0, 9.50.0, 9.51, 9.52, 11.0.0.0, 11.50, or any version 11.51 or lower
-
Check LoadRunner version via Program Files directoryNavigate to C:\Program Files\HP\LoadRunner\ or C:\Program Files\Mercury Interactive\LoadRunner\ and locate the launcher or bin directory. Right-click on the LoadRunner executable and view Properties > Details for the version numberAffected if The version shown is 9.0.0, 9.50.0, 9.51, 9.52, 11.0.0.0, 11.50, or 11.51 or lower
-
Check LoadRunner version via Help > About in the applicationLaunch the LoadRunner application (VuGen, Controller, or Analysis) and navigate to Help > About to view the exact product versionAffected if The reported version is 11.51 or lower, or exactly matches 9.0.0, 9.50.0, 9.51, 9.52, 11.0.0.0, or 11.50
-
Check installed HP LoadRunner componentsOpen Windows Control Panel > Programs and Features and look for HP LoadRunner entries. Note all installed component versions listedAffected if Any installed component shows version 11.51 or below, or matches the specific affected versions listed
You are affected if HP LoadRunner is installed with any version from 9.0.0 through 11.51, or specifically 9.50.0, 9.51, 9.52, 11.0.0.0, or 11.50.
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 dataUpgrade HP LoadRunner to version 11.52 or later. If immediate upgrade is not feasible, restrict network access to LoadRunner components and implement network segmentation to limit exposure.
- Consultation6.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-2369 — 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-2013-2369 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