CVE-2009-0712
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 · uneditedUnspecified vulnerability in WMI Mapper for HP Systems Insight Manager before 2.5.2.0 allows local users to gain privileges via unknown 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 confidenceLocal privilege escalation vulnerability in the WMI Mapper component of HP Systems Insight Manager versions prior to 2.5.2.0. The vulnerability allows local authenticated users to gain elevated privileges through unspecified vectors, likely involving manipulation of WMI permissions or service configuration.
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 dataall versionsCVSS 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
- Local
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify HP Systems Insight Manager installationCheck for HP Systems Insight Manager in installed programs via Windows Registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or use 'Get-ItemProperty' PowerShell command against the uninstall registry keysAffected if HP Systems Insight Manager is present on the system
-
Determine installed version of HP Systems Insight ManagerQuery the version from registry key HKLM\SOFTWARE\HP\SystemsInsightManager\CurrentVersion or check the 'DisplayVersion' value in the uninstall registry entryAffected if Version is found to be lower than 2.5.2.0 or version cannot be determined (indicating an older release)
-
Confirm WMI Mapper service presenceCheck for the HP WMI Mapper service using 'Get-Service | Where-Object {$_.Name -like '*WMI*'}' or 'sc query' command. Look for service names containing 'HPWMI' or 'WmiMapper'Affected if The HP WMI Mapper service exists and is installed on the system
-
Inspect WMI permissions configurationReview WMI control security settings via 'wmimgmt.msc' or programmatically via WMI Explorer to check for non-administrative users granted elevated WMI access permissionsAffected if WMI security settings allow authenticated users or low-privilege accounts to access sensitive namespaces or methods used by the mapper component
-
Verify service execution contextRun 'sc qc HPWmiMapper' (or similar service name) to check the service binary path and startup type configuration for the WMI Mapper serviceAffected if The service is configured to run with elevated privileges and allows local authenticated users to interact with it
A system is affected if HP Systems Insight Manager with WMI Mapper component is installed and the version is below 2.5.2.0, or if the WMI Mapper service exists with permissive access controls allowing local authenticated users to manipulate WMI permissions or service configuration for privilege escalation.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade HP Systems Insight Manager to version 2.5.2.0 or later. Until upgrade is possible, limit local system access to trusted administrative users only and monitor for suspicious WMI activity.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-0712 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2009-0712 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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