OneviewApplication · Hp

CVE-2014-2602

MEDIUM · 6.5 CVSS v2.0 Published 2014-05-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
Unspecified vulnerability in HP OneView 1.0 and 1.01 allows remote authenticated 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 confidence

HP OneView versions 1.0 and 1.01 contain an unspecified vulnerability allowing remote authenticated users to elevate their privileges beyond what their current role should permit. The attack vector is remote and requires valid authentication, but the exact exploitation method is not disclosed.

MitigationUpdate HP OneView to the latest patched version and review user role assignments to ensure least-privilege access controls are enforced.

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
OneviewApplication
Affected:= 1.0= 1.01

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
Single
Confidentiality
Partial
Integrity
Partial
Availability
Partial

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

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. Confirm HP OneView is installed
    Check system for HP OneView application by searching for OneView installation directories or checking running services (e.g., service hpov* status on Linux, or look for HP OneView processes in Windows Task Manager)
    Affected if HP OneView software is present on the system
  2. Identify installed HP OneView version
    Access the HP OneView web interface and navigate to About section, or check the installer version via command line if available (common paths: /opt/hp/oneview or C:\Program Files\HP\OneView). Also check the HP OneView appliance management console for version information.
    Affected if Version displayed is exactly 1.0 or 1.01
  3. Verify remote access is enabled
    Check HP OneView network settings in the administration console to confirm remote access or API access is enabled. Review firewall rules and network exposure of the OneView management interface.
    Affected if Remote network access to the OneView interface is permitted from non-trusted networks
  4. Review active user accounts and roles
    Log into HP OneView as administrator and navigate to User Management or Access Control section to list all users and their assigned roles. Note any users with elevated or administrative roles.
    Affected if Multiple user accounts exist with varying privilege levels, particularly any accounts beyond the default administrator
  5. Check authentication configuration
    Examine HP OneView authentication settings (Local Authentication, Active Directory/LDAP integration) in the administration console to confirm how user authentication is configured and whether external authentication sources are in use.
    Affected if Authentication is configured to allow remote user logins

User is affected if HP OneView versions 1.0 or 1.01 are running with remote access enabled and multiple authenticated users exist, allowing potential privilege escalation beyond assigned roles.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update HP OneView to the latest patched version and review user role assignments to ensure least-privilege access controls are enforced.

Fix this in Oneview Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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