Oneview Global DashboardApplication · Hpe

CVE-2023-28085

MEDIUM · 5.5 CVSS v3.1 Published 2023-04-14
Fix available
A fix is available. Upgrade to 2.72 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
An HPE OneView Global Dashboard (OVGD) appliance dump may expose OVGD user account credentials

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

The HPE OneView Global Dashboard appliance generates dump files that may contain sensitive user account credentials in plaintext. An attacker with access to these dump files could retrieve valid OVGD user credentials and potentially pivot to other systems.

MitigationRestrict access to appliance dump files, implement secure credential storage (hashing/salting), rotate any exposed credentials, and ensure dumps exclude sensitive authentication data.

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
Oneview Global DashboardApplication
Affected:< 2.72

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. Identify HPE OneView Global Dashboard installation
    Locate the HPE OneView Global Dashboard appliance in your environment and confirm it is running as a standalone appliance or virtual appliance.
    Affected if HPE OneView Global Dashboard is not present in the environment.
  2. Check installed version
    Access the appliance administration interface or use the appliance's version check command to determine the installed version number.
    Affected if The installed version is lower than 2.72.
  3. Locate dump files
    Search the appliance file system for dump files, typically found in diagnostic or logs directories. Check common dump file locations such as /var/log, /tmp, or diagnostic export folders.
    Affected if Dump files exist on the appliance.
  4. Inspect dump file contents for credentials
    Open a sample dump file and search for plaintext strings that resemble user credentials, passwords, or authentication tokens. Look for patterns like 'password=', 'credential=', or plain text username:password combinations.
    Affected if Dump files contain plaintext user credentials or authentication data.

A user is affected if HPE OneView Global Dashboard version is below 2.72 AND dump files exist on the appliance that contain plaintext credentials.

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 2.72 or later
Fixed in 2.72
Interim mitigation

Restrict access to appliance dump files, implement secure credential storage (hashing/salting), rotate any exposed credentials, and ensure dumps exclude sensitive authentication data.

Recommended fix Moderate confidence

Version 2.72 or later

  1. Back up the current HPE OneView Global Dashboard configuration and any critical data
  2. Download the HPE OneView Global Dashboard version 2.72 or later from support.hpe.com
  3. Review HPE's official upgrade documentation for OVGD before proceeding
  4. Apply the upgrade to the OVGD appliance following HPE's documented upgrade procedure
  5. After upgrade, verify the OVGD appliance is functioning correctly
  6. Confirm the appliance dump functionality no longer exposes user credentials
Caveat Standard upgrade risks apply - ensure backup before proceeding

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

Fix this in Oneview Global Dashboard Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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