CVE-2013-4797
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-1690.
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 versions prior to 11.52 contain an unspecified vulnerability (ZDI-CAN-1690) that allows remote attackers to execute arbitrary code via unknown vectors. The CVSS 7.5 score indicates a network-exploitable flaw requiring no authentication with complete impact on confidentiality, integrity, and availability.
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 versionOpen Windows Control Panel > Programs and Features (or Add or Remove Programs), locate HP LoadRunner in the list, and note the version columnAffected if The displayed version is 11.51 or lower, or shows exactly 9.0.0, 9.50.0, 9.51, 9.52, 11.0.0.0, or 11.50
-
Check LoadRunner About dialogLaunch the LoadRunner launcher ( VuGen, Controller, or Analysis), then navigate to Help > About and record the version information shownAffected if The About dialog reports any version prior to 11.52 or any of the specific affected versions listed
-
Check Windows registry for versionOpen Registry Editor (regedit), navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Mercury Interactive\LoadRunner\ or HKEY_LOCAL_MACHINE\SOFTWARE\HP\LoadRunner\ (if present), and examine the Version or VersionString valueAffected if The registry Version value indicates a version <= 11.51 or matches 9.0.0, 9.50.0, 9.51, 9.52, 11.0.0.0, or 11.50
-
Verify executable file versionLocate the main LoadRunner executable (typically in the bin folder, such as wlrun.exe or VuGen.exe), right-click the file, select Properties, and check the Details tab for Product VersionAffected if The Product Version shown is any version prior to 11.52 or matches the specific affected versions
If HP LoadRunner is installed and the version is 11.51 or lower, or exactly 9.0.0, 9.50.0, 9.51, 9.52, 11.0.0.0, or 11.50, the environment is affected by this vulnerability.
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 to remediate this vulnerability. If immediate upgrade is not feasible, restrict network access to LoadRunner components and monitor for indicators of compromise.
- Consultation2.0 h
- Implementation4.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-4797 — 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-4797 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