dbcve.org
Power ManagerApplication · Hp

CVE-2009-4000

HIGH · 10.0 CVSS v2.0 Published 2010-01-20
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
Directory traversal vulnerability in goform/formExportDataLogs in HP Power Manager before 4.2.10 allows remote attackers to overwrite arbitrary files, and execute arbitrary code, via directory traversal sequences in the fileName parameter.

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.2.10 contain a directory traversal vulnerability in the goform/formExportDataLogs web handler. Attackers can exploit this by injecting directory traversal sequences (e.g., ../../../) into the fileName parameter to write arbitrary files to the filesystem, potentially achieving remote code execution.

MitigationUpgrade HP Power Manager to version 4.2.10 or later to obtain the vendor patch. If immediate patching is not possible, implement input validation to reject directory traversal sequences in the fileName parameter and restrict web server write permissions.

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
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. Check if HP Power Manager is installed
    Look for HP Power Manager installation directory (typically C:\Program Files\HP\Power Manager or C:\Program Files (x86)\HP\Power Manager) and check for hppm.exe process running
    Affected if HP Power Manager software is present on the system and the web service component is active
  2. Determine installed version
    Locate the HP Power Manager installation and check version information in the software (usually via help > about or by right-clicking hppm.exe and selecting properties)
    Affected if Installed version is 4.2.5, 4.2.6, 4.2.7, 4.2.8, or any version prior to 4.2.10
  3. Verify web service is running
    Check if the HP Power Manager web server is active by attempting to access the web interface (default port 80 or 443) or by checking for hppmweb.exe or similar web service process
    Affected if The web interface is enabled and accessible on the network
  4. Test vulnerable endpoint accessibility
    Attempt to access the vulnerable URL path: /goform/formExportDataLogs - check if the web handler responds (even with an error) indicating the endpoint exists
    Affected if The web handler responds, indicating the vulnerable code path is present and reachable
  5. Inspect web server logs for exploitation attempts
    Review HP Power Manager web server logs for entries containing directory traversal patterns such as ../ in the fileName parameter
    Affected if Log entries show directory traversal sequences in requests to formExportDataLogs handler

HP Power Manager version 4.2.9 or below is installed AND the web interface is enabled and accessible, making the formExportDataLogs handler reachable for exploitation.

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.2.10 or later to obtain the vendor patch. If immediate patching is not possible, implement input validation to reject directory traversal sequences in the fileName parameter and restrict web server write permissions.

Recommended fix High confidence

Power Manager 4.2.10

  1. 1. Download HP Power Manager version 4.2.10 or later from the official HP support website
  2. 2. Back up the current Power Manager configuration and data
  3. 3. Stop the Power Manager service
  4. 4. Install the updated Power Manager 4.2.10 version
  5. 5. Restore the configuration from the backup if needed
  6. 6. Start the Power Manager service
  7. 7. Verify the version by checking the Power Manager About or version information

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

Fix this in Power Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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