Security readout for executives and security teams
Plain-English summary
HP LoadRunner versions before 11.52 have an unspecified flaw that can let a remote attacker run arbitrary code. The public record does not explain the attack path, affected component, or prerequisites. Treat this as serious where legacy LoadRunner systems remain in use.
Executive priority
Prioritize remediation if LoadRunner is still present, especially on reachable or shared infrastructure. The vulnerability enables remote code execution, but public evidence is incomplete and does not support claims of active exploitation.
Technical view
CVE-2013-2370 describes an unspecified remote code execution vulnerability in HP LoadRunner before 11.52, also tracked as ZDI-CAN-1671. The source bundle provides no CVSS score, CWE, affected component, or vector details, so exposure assessment depends on local version inventory and vendor advisory review.
Likely exposure
Exposure is most likely in organizations still running HP LoadRunner earlier than 11.52. Risk is higher if those systems are reachable by untrusted networks, shared testing environments, or users outside the performance testing team.
Exploitation context
The provided sources do not show known active exploitation, and the CVE is not listed as KEV. Public details are limited to remote arbitrary code execution via unknown vectors, so exploitation likelihood cannot be confirmed from this bundle.
Researcher notes
Key gaps are the unknown attack vector, affected component, prerequisites, and scoring data. Analysis should stay anchored to HP SSRT101083 and the CVE record; do not infer affected modules or exploit mechanics without additional vendor-backed evidence.
Mitigation direction
- Inventory HP LoadRunner deployments and identify versions earlier than 11.52.
- Upgrade affected LoadRunner installations to 11.52 or newer per HP guidance.
- Review HP SSRT101083 for vendor-specific remediation and support status.
- Restrict access to legacy LoadRunner systems until remediation is complete.
- Retire unsupported instances where upgrade guidance cannot be applied.
Validation and detection
- Confirm all LoadRunner installations report version 11.52 or newer.
- Check asset inventory for unmanaged or forgotten LoadRunner systems.
- Review network exposure for LoadRunner hosts and related services.
- Verify change records show the HP advisory remediation was applied.
- Monitor legacy hosts for unexpected service behavior or unauthorized process execution.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
Execution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2013-2370 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- SSRT101083CVE reference · vendor-advisory, x_refsource_HP
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.