CVE-2013-2368
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 cause a denial of service via unknown vectors, aka ZDI-CAN-1669.
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 · low confidenceHP LoadRunner before version 11.52 contains an unspecified vulnerability that allows remote attackers to cause a denial of service via unknown vectors. The vulnerability is identified as ZDI-CAN-1669 and carries a CVSS score of 5 (MEDIUM).
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
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/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.
-
Locate HP LoadRunner installation and versionOpen HP LoadRunner and go to Help > About, or check the installation directory for a version file. Alternatively, check Windows Programs and Features (Add/Remove Programs) for the installed version number.Affected 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.
-
Confirm LoadRunner components are exposedIdentify if the LoadRunner server components (such as the Load Generator or Controller service) are running and accessible on the network. Check running services via Windows Services console or netstat commands for listening ports associated with LoadRunner.Affected if LoadRunner services are running and accessible from the network, making them potentially reachable by remote attackers.
-
Verify version is below 11.52Compare your identified version number against the safe version 11.52. The vulnerability exists in any version before 11.52, including all listed affected versions.Affected if The installed version is any build earlier than 11.52, placing it within the vulnerable version range.
If HP LoadRunner is installed and the version is 11.51 or lower, or specifically matches 9.0.0, 9.50.0, 9.51, 9.52, 11.0.0.0, or 11.50, the environment is affected by this CVE.
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. As a temporary mitigation, restrict network access to LoadRunner components if upgrade is not immediately feasible.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2013-2368 — 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-2368 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