dbcve.org
NimbleosOperating system · Hpe

CVE-2022-28618

CRITICAL · 9.8 CVSS v3.1 Published 2022-05-20
Fix available
A fix is available. Upgrade to 5.0.10.100 / 5.2.1.500 or later.
See remediation →
100/100
Remediation priority · Urgent
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
A command injection security vulnerability has been identified in HPE Nimble Storage Hybrid Flash Arrays, HPE Nimble Storage All Flash Arrays and HPE Nimble Storage Secondary Flash Arrays that could allow an attacker to execute arbitrary commands on a Nimble appliance. HPE has made the following software updates to resolve the vulnerability in HPE Nimble Storage: 5.0.10.100 or later, 5.2.1.0 or later, 6.0.0.100 or later.

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

A command injection vulnerability in HPE Nimble Storage arrays allows authenticated attackers to execute arbitrary commands on the appliance through unsanitized input in the management interface. This enables full compromise of the storage system.

MitigationApply the appropriate software update (5.0.10.100+, 5.2.1.0+, or 6.0.0.100+) following HPE's update procedure and verify the patch resolves the injection vector.

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
NimbleosOperating system
Affected:< 5.0.10.100>= 5.1.0.0, < 5.2.1.500>= 5.3.0.0, < 6.0.0.100

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

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

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. Retrieve the installed Nimbleos version
    Log into the HPE Nimble Storage management interface (web GUI or CLI). In the web GUI, go to System > Overview or Help > About to view the OS version. Via CLI, run 'show system' or 'nimblectl get system' to display the version information.
    Affected if The displayed version is less than 5.0.10.100, or between 5.1.0.0 and 5.2.1.499, or between 5.3.0.0 and 6.0.0.099
  2. Verify management interface network exposure
    Confirm whether the Nimble management interface (HTTPS on ports 5392/5432 or SSH on port 22) is accessible from network segments outside the trusted admin zone. Check firewall rules, VLAN configuration, or perform a port scan from an external perspective.
    Affected if The management interface is reachable from untrusted networks, increasing the likelihood of credential-based exploitation
  3. Confirm authentication to management interface is possible
    Determine if any user accounts exist with access to the Nimble storage array management interface. This includes local users, LDAP/Active Directory integrated users, or service accounts with management privileges.
    Affected if The management interface accepts authentication and the vulnerability requires valid credentials to execute the command injection

You are affected if your Nimbleos version falls within the vulnerable ranges (less than 5.0.10.100, 5.1.0.0-5.2.1.499, or 5.3.0.0-6.0.0.099) and the management interface is network-accessible with valid authentication available.

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 5.0.10.100 / 5.2.1.500 / 6.0.0.100 or later
Fixed in 5.0.10.1005.2.1.5006.0.0.100
Interim mitigation

Apply the appropriate software update (5.0.10.100+, 5.2.1.0+, or 6.0.0.100+) following HPE's update procedure and verify the patch resolves the injection vector.

Recommended fix High confidence

NimbleOS 5.0.10.100 or later (5.0.x branch), 5.2.1.0 or later (5.2.x branch), or 6.0.0.100 or later (6.0.x branch)

  1. 1. Back up all critical data and configuration on the Nimble Storage array before initiating any upgrade.
  2. 2. Review the current NimbleOS version by logging into the Nimble UI or using the CLI: 'nimblectl show array'.
  3. 3. Determine the appropriate upgrade path based on current version: If on 5.0.x branch, upgrade to 5.0.10.100 or later. If on 5.1.x or 5.2.x branch, upgrade to 5.2.1.0 or later. If on 5.3.x branch, upgrade to 6.0.0.100 or later.
  4. 4. Download the appropriate NimbleOS firmware from the HPE support site (support.hpe.com) using your HPE account.
  5. 5. Schedule a maintenance window as upgrades may cause temporary service interruption.
  6. 6. Upload the firmware to the Nimble array via the Nimble UI (System > Updates) or CLI.
  7. 7. Initiate the upgrade and monitor progress through the management interface.
  8. 8. After upgrade completes, verify the new version: 'nimblectl show array' and confirm it shows 5.0.10.100+, 5.2.1.0+, or 6.0.0.100+.
Caveat Storage array upgrades may cause temporary service disruption; plan maintenance window accordingly

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

Fix this in Nimbleos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
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,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-28618 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2022-28618 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