CVE-2013-2370
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-1671.
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. The vulnerability is network-exploitable (CVSS 7.5) and requires no authentication, indicating a pre-authentication RCE flaw in the LoadRunner 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<= 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.
-
Identify installed HP LoadRunner versionCheck the Windows registry key HKLM\SOFTWARE\Mercury Interactive\LoadRunner for the Version value, or examine the LoadRunner installation directory (typically C:\Program Files\HP\LoadRunner) for version information in product info files.Affected if The installed version matches 9.0.0, 9.50.0, 9.51, 9.52, 11.0.0.0, 11.50, or any version lower than or equal to 11.51.
-
Verify LoadRunner services are runningOpen Windows Services console (services.msc) or use command 'sc query' to enumerate running services. Look for HP LoadRunner services such as LoadRunner Agent Service, LoadRunner Manager, or LoadRunner Magistrate.Affected if Any LoadRunner services are in a running state, as the vulnerability is exploitable when the LoadRunner component is active.
-
Check network exposure of LoadRunner portsUse netstat -an or PowerShell Get-NetTCPConnection to identify ports on which LoadRunner is listening. Common ports include 54345 (Agent), 50500 (Management), and 8080-8090 (Web). Verify if these listen on 0.0.0.0 or external adapters rather than 127.0.0.1.Affected if LoadRunner services are bound to accessible network interfaces (0.0.0.0 or external IP) rather than localhost only, making the pre-authentication flaw network-exploitable.
You are affected if HP LoadRunner version is 9.0.0, 9.50.0, 9.51, 9.52, 11.0.0.0, 11.50, or any version through 11.51, and the LoadRunner component is running and network-accessible.
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, consider network segmentation to limit exposure of LoadRunner systems and restrict access to the management interfaces.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-2370 — 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-2370 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