dbcve.org
DiagnosticsApplication · Hp

CVE-2011-4789

HIGH · 10.0 CVSS v2.0 Published 2012-01-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
High EPSS 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
Stack-based buffer overflow in magentservice.exe in the server in HP LoadRunner 11.00 before patch 4 allows remote attackers to execute arbitrary code via a crafted size value in a packet. NOTE: it was originally reported that the affected product is HP Diagnostics Server, but HP states that "the vulnerable product is actually HP LoadRunner."

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 · high confidence

Stack-based buffer overflow in magentservice.exe in HP LoadRunner 11.00 allows remote attackers to execute arbitrary code via a crafted size value in a packet. The vulnerability exists in the server component's packet handling logic, which fails to properly validate the size value before copying data into a fixed-size stack buffer.

MitigationApply HP LoadRunner 11.00 Patch 4 or later to address the buffer overflow vulnerability. If patching is not feasible, restrict network access to the magentservice.exe 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
DiagnosticsApplication
Affected:all versions

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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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. Locate magentservice.exe on the system
    Search for magentservice.exe in typical HP installation directories (e.g., C:\Program Files\HP\LoadRunner\ or C:\Program Files\HP\Diagnostics\) or use: dir /s C:\magentservice.exe on Windows
    Affected if The file magentservice.exe exists on the system and corresponds to an unpatched HP LoadRunner 11.00 or HP Diagnostics installation
  2. Identify installed HP software and version
    Check Add/Remove Programs or the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for HP LoadRunner or HP Diagnostics entries. Look for version information in the registry or program directory.
    Affected if HP LoadRunner 11.00 without Patch 4 or later, or HP Diagnostics of any version with the vulnerable magentservice.exe component present
  3. Verify if magentservice.exe is running and exposed
    Open Task Manager or run: tasklist | findstr magentservice.exe to check if the process is active. Use netstat -an to check if the service is listening on network ports (typically port 5435 for MagentService).
    Affected if magentservice.exe is running and bound to a network interface accessible to attackers, creating an exploitable attack surface
  4. Confirm patch level for LoadRunner 11.00
    Check the HP LoadRunner installation for installed patches. Look in the installation directory for patch-related files or check HP Support website for patch version metadata.
    Affected if The installation is HP LoadRunner 11.00 with Patch 4 or earlier applied (patch not installed), indicating the vulnerability is present

A user is affected if HP Diagnostics (any version) or HP LoadRunner 11.00 without Patch 4 is installed with the magentservice.exe component present and running, exposing the vulnerable packet handling logic to network attackers.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply HP LoadRunner 11.00 Patch 4 or later to address the buffer overflow vulnerability. If patching is not feasible, restrict network access to the magentservice.exe component.

Recommended fix Moderate confidence

HP LoadRunner 11.00 Patch 4

  1. Identify the current installed version of HP LoadRunner 11.00
  2. Obtain HP LoadRunner 11.00 Patch 4 from the official HP support website (h20565.www2.hp.com)
  3. Apply the patch following HP's standard patch installation procedures
  4. Restart the magentservice.exe service if required after patching
  5. Verify the patch was applied successfully by checking the version
Caveat Patch should be backward compatible; test in non-production environment first if possible

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Diagnostics Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2011-4789 — 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-2011-4789 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