Onboard AdministratorApplication · Hp

CVE-2012-0129

HIGH · 7.6 CVSS v2.0 Published 2012-04-05
Fix available
A fix is available. Upgrade to after 3.32 or later.
See remediation →
85/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
HP Onboard Administrator (OA) before 3.50 allows remote attackers to bypass intended access restrictions and execute arbitrary code 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

HP Onboard Administrator (OA) before version 3.50 contains an access control bypass vulnerability that allows remote attackers to circumvent intended security restrictions and execute arbitrary code on the targeted system. The attack vector is remote and network-based, suggesting the vulnerability involves improper authentication or authorization checks in the OA management interface.

MitigationUpgrade HP Onboard Administrator to version 3.50 or later to remediate this vulnerability. As this flaw allows remote code execution, prompt patching is critical given the CVSS score of 7.6.

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
Onboard AdministratorApplication
Affected:<= 3.32= 1.00= 1.01= 1.10= 1.11= 1.12= 1.20= 1.30= 2.01= 2.02= 2.04= 2.10

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

AV:N/AC:H/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. Identify HP Onboard Administrator installation
    Locate the OA management interface. This is typically accessed via a web browser to the OA IP address or hostname (often on port 80/443). Check network documentation or scan for devices responding on typical OA management ports.
    Affected if HP OA is present and accessible on the network
  2. Determine installed OA version
    Log into the OA web interface and navigate to the version information page, typically found under 'General Information' or 'About' in the navigation menu. The version number is displayed prominently on this page.
    Affected if Version displayed is 3.50 or lower, or matches any of these: 1.00, 1.01, 1.10, 1.11, 1.12, 1.20, 1.30, 2.01, 2.02, 2.04, 2.10, or any version <= 3.32
  3. Verify remote management is enabled
    Check OA configuration settings for remote management access. In the OA web interface, examine the 'Network Settings' or 'Access Settings' section to confirm the management interface is network-accessible rather than local-only.
    Affected if Remote management is enabled and the OA interface is reachable over the network (this is the default configuration)
  4. Confirm OA is exposed to network
    Determine if the OA management port (default HTTP port 80 or HTTPS port 443) is accessible from external or untrusted network segments. Use network scanning tools or review firewall rules to identify exposed OA instances.
    Affected if The OA management interface is exposed to untrusted network segments or the internet

The system is affected if HP Onboard Administrator version 3.50 or lower is installed, the OA management interface is network-accessible, and remote attackers can reach the management portal.

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

Upgrade HP Onboard Administrator to version 3.50 or later to remediate this vulnerability. As this flaw allows remote code execution, prompt patching is critical given the CVSS score of 7.6.

Fix this in Onboard Administrator Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-0129 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2012-0129 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