OneviewApplication · Hp

CVE-2023-28091

MEDIUM · 5.5 CVSS v3.1 Published 2023-04-14
Fix available
A fix is available. Upgrade to after 8.1 or later.
See remediation →
57/100
Remediation priority · Elevated
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
HPE OneView virtual appliance "Migrate server hardware" option may expose sensitive information in an HPE OneView support dump

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

In HPE OneView virtual appliance, the 'Migrate server hardware' feature has an information disclosure vulnerability where sensitive data may be written to support dump files. An attacker with access to these dumps could obtain the exposed sensitive information.

MitigationApply the HPE OneView patch when available. Until patched, restrict access to support dumps and monitor for unauthorized access to these files.

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:>= 7.0, <= 8.1

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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 HPE OneView version
    Check the installed HPE OneView virtual appliance version and compare it against the affected range: 7.0 through 8.1
    Affected if The installed version falls within >= 7.0 and <= 8.1
  2. Identify use of Migrate server hardware feature
    Review HPE OneView logs, audit trails, or configuration records to determine whether the 'Migrate server hardware' feature has been used
    Affected if The feature was invoked, causing sensitive data to potentially be written to dump files
  3. Locate support dump files
    Access the support dump storage location on the HPE OneView appliance and enumerate any dump files present
    Affected if Support dump files exist on the system
  4. Check access to support dumps
    Review file permissions and access logs for the support dump directory to determine if unauthorized access may have occurred
    Affected if Support dumps are accessible to unauthorized users or have been accessed by unexpected accounts

A user is affected if their HPE OneView version is between 7.0 and 8.1, the Migrate server hardware feature was used, and sensitive data may have been written to accessible support dump files.

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 8.1
Interim mitigation

Apply the HPE OneView patch when available. Until patched, restrict access to support dumps and monitor for unauthorized access to these files.

Recommended fix Moderate confidence

Contact HPE for the specific fixed release beyond version 8.1

  1. Contact HPE Support or visit support.hpe.com to obtain the specific patch or updated version that addresses CVE-2023-28091
  2. Verify with HPE that the fix for the 'Migrate server hardware' information disclosure is included in the version you plan to upgrade to
  3. Before upgrading, ensure you have a complete backup of the HPE OneView virtual appliance
  4. Plan for maintenance window as upgrade may require downtime
  5. After upgrading, generate a new support dump and verify that sensitive information is no longer exposed in the 'Migrate server hardware' related data
  6. Review HPE OneView release notes for any security fixes included in the new version
Caveat Review HPE OneView upgrade documentation for any compatibility considerations or configuration changes required when moving from affected versions

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

Fix this in Oneview 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-2023-28091 — 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-2023-28091 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