dbcve.org
Power ManagerApplication · Hp

CVE-2010-4113

HIGH · 9.3 CVSS v2.0 Published 2010-12-22
Fix available
A fix is available. Upgrade to after 4.2.9 or later.
See remediation →
100/100
Remediation priority · Urgent
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 HP Power Manager (HPPM) before 4.3.2 allows remote attackers to execute arbitrary code via a long Login variable to the management web server.

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

HP Power Manager versions prior to 4.3.2 contain a stack-based buffer overflow vulnerability in the web management interface. Attackers can exploit this by sending an overly long Login variable value, which overflows a stack buffer and allows arbitrary code execution with the privileges of the web service.

MitigationUpgrade HP Power Manager to version 4.3.2 or later. If immediate patching is not possible, restrict network access to the management web server to trusted IPs only, or disable the web management interface until the patch can be applied.

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
Power ManagerApplication
Affected:<= 4.2.9= 4.2.5= 4.2.6= 4.2.7= 4.2.8

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

AV:N/AC:M/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. Verify HP Power Manager is installed
    Check for the HP Power Manager service or executable. On Windows, look for the service named 'HP Power Manager' in Services or check for C:\Program Files\HP\Power Manager\ppm.exe
    Affected if The software is not found on the system - not applicable
  2. Determine the installed version
    Right-click on the ppm.exe executable (typically in C:\Program Files\HP\Power Manager\) and select Properties, then view the Version tab. Alternatively, check the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\Power Manager for the Version value.
    Affected if The installed version is 4.2.5, 4.2.6, 4.2.7, 4.2.8, or any version lower than or equal to 4.2.9
  3. Confirm the web management interface is enabled
    Check if the HP Power Manager web service is running. Open a browser and attempt to access the management interface at https://localhost:2381 or http://localhost:2381. Also verify the service is started in Windows Services.
    Affected if The web management interface is accessible and responds to requests - the vulnerability requires this to be active
  4. Check network exposure
    Verify if the web management port (default 2381) is bound to external network interfaces. Run 'netstat -an | findstr 2381' and confirm if LISTENING on 0.0.0.0:2381 or :::2381 indicates external accessibility.
    Affected if The web interface is listening on external IP addresses rather than localhost only - increases exposure risk

You are affected if HP Power Manager is installed with a version between 4.2.5 and 4.2.9 (inclusive) and the web management interface is enabled and accessible.

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
Upgrade available Upgrade to a release after 4.2.9
Interim mitigation

Upgrade HP Power Manager to version 4.3.2 or later. If immediate patching is not possible, restrict network access to the management web server to trusted IPs only, or disable the web management interface until the patch can be applied.

Recommended fix High confidence

4.3.2

  1. Back up the current HP Power Manager configuration and data
  2. Download HP Power Manager version 4.3.2 or later from HP's official support website
  3. Stop the HP Power Manager service
  4. Install version 4.3.2 or later following HP's installation documentation
  5. Restore the configuration from the backup if needed
  6. Start the HP Power Manager service
  7. Verify the upgrade was successful by checking the version number in the management interface

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

Fix this in Power Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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