dbcve.org
Performance CenterApplication · Hp

CVE-2016-4361

HIGH · 7.5 CVSS v3.0 Published 2016-06-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
HPE LoadRunner 11.52 through patch 3, 12.00 through patch 1, 12.01 through patch 3, 12.02 through patch 2, and 12.50 through patch 3 and Performance Center 11.52 through patch 3, 12.00 through patch 1, 12.01 through patch 3, 12.20 through patch 2, and 12.50 through patch 1 allow remote attackers to cause a denial of service via unspecified vectors.

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 confidence

HPE LoadRunner and Performance Center contain a denial of service vulnerability that can be exploited remotely by attackers. The vulnerability affects multiple version ranges across both products (LoadRunner 11.52-12.50 and Performance Center 11.52-12.50) across various patch levels, allowing unspecified vectors to cause service disruption.

MitigationApply the appropriate vendor patches for the specific version of LoadRunner or Performance Center in use. For LoadRunner: patch 4 or later for 11.52/12.00/12.01/12.02, patch 4 or later for 12.50. For Performance Center: patch 4 or later for 11.52/12.00/12.01/12.20, patch 2 or later for 12.50.

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
Performance CenterApplication
Affected:= 11.52= 12.00= 12.01= 12.20= 12.50
LoadrunnerApplication
Affected:= 11.52= 12.00= 12.01= 12.02= 12.50

CVSS 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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed HPE product
    Check system for HPE LoadRunner or Performance Center installation by looking for installation directories (commonly in C:\Program Files\HP\LoadRunner or C:\HP\Performance Center) or look for running services named 'LoadRunner' or 'Performance Center' in Windows Services or running processes
    Affected if Either HPE LoadRunner or HPE Performance Center is installed on the system
  2. Determine exact product version
    Open the product and navigate to Help > About, or check the version in the installation directory by locating a version file or checking the executable properties (right-click on the main executable and select Properties > Details for version information)
    Affected if The installed version matches exactly: LoadRunner 11.52, 12.00, 12.01, 12.02, or 12.50; OR Performance Center 11.52, 12.00, 12.01, 12.20, or 12.50
  3. Check installed patches
    Look in the installation directory for a patch folder or check Add/Remove Programs for installed updates. The product documentation or HP Support site can confirm patch levels. For LoadRunner 12.50, verify if Patch 4 or later is applied; for LoadRunner 11.52/12.00/12.01/12.02, verify Patch 4 or later; for Performance Center 12.50 verify Patch 2 or later; for Performance Center 11.52/12.00/12.01/12.20 verify Patch 4 or later
    Affected if The product is an affected version AND the appropriate vendor patch (Patch 4 for most versions, Patch 2 for PC 12.50) has NOT been applied

A user is affected if HPE LoadRunner or Performance Center is installed and the version is 11.52, 12.00, 12.01, 12.02, 12.20, or 12.50 without the corresponding vendor patch applied.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the appropriate vendor patches for the specific version of LoadRunner or Performance Center in use. For LoadRunner: patch 4 or later for 11.52/12.00/12.01/12.02, patch 4 or later for 12.50. For Performance Center: patch 4 or later for 11.52/12.00/12.01/12.20, patch 2 or later for 12.50.

Fix this in Performance Center Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-4361 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-4361 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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