dbcve.org
NimbleosOperating system · Hpe

CVE-2022-23705

HIGH · 7.5 CVSS v3.1 Published 2022-05-09
Fix available
A fix is available. Upgrade to 5.0.10.100 / 5.2.1.500 or later.
See remediation →
84/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
A 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 which could potentially allow the upload, but not execution, of unauthorized update binaries to the array. 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 · moderate confidence

A vulnerability in HPE Nimble Storage arrays allows unauthorized upload of update binaries to the array, though the uploaded binaries cannot be executed. This represents a file upload authorization bypass that could potentially be combined with other vulnerabilities for further exploitation, though the description explicitly states execution is blocked.

MitigationUpgrade HPE Nimble Storage arrays to version 5.0.10.100 or later, 5.2.1.0 or later, or 6.0.0.100 or later to remediate this vulnerability.

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.1.0

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 the device as HPE Nimble Storage
    Confirm the storage system is an HPE Nimble Storage array by checking the system model, management interface, or CLI output (nimblectl).
    Affected if The system is an HPE Nimble Storage array.
  2. Determine the NimbleOS version
    Use the HPE Nimble Storage management interface (SMU or web UI), CLI (nimblectl), or API to retrieve the installed NimbleOS version. Typically found in system info or about section.
    Affected if Unable to retrieve a NimbleOS version.
  3. Compare the installed version against affected ranges
    Check if the installed NimbleOS version falls into any of these affected ranges: versions earlier than 5.0.10.100, OR versions 5.1.0.0 through 5.2.1.500 (excluding 5.2.1.500), OR version 5.3.1.0 exactly.
    Affected if The installed version is earlier than 5.0.10.100, OR is 5.1.0.0 through 5.2.1.499, OR is exactly 5.3.1.0.
  4. Note the limitation of this vulnerability
    Understand that this CVE allows unauthorized upload of update binaries but the description states uploaded binaries cannot be executed. This is an authorization bypass that could be combined with other vulnerabilities.
    Affected if The system is in the affected version range and could be targeted for unauthorized file upload.

You are affected if your HPE Nimble Storage array runs NimbleOS version earlier than 5.0.10.100, between 5.1.0.0 and 5.2.1.499, or exactly version 5.3.1.0.

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

Upgrade HPE Nimble Storage arrays to version 5.0.10.100 or later, 5.2.1.0 or later, or 6.0.0.100 or later to remediate this vulnerability.

Recommended fix High confidence

NimbleOS 5.0.10.100+ (for 5.0.x), NimbleOS 5.2.1.0+ (for 5.1.x-5.2.x), or NimbleOS 6.0.0.100+ (recommended for 5.3.x)

  1. 1. Identify the current installed NimbleOS version by accessing the array management interface or using the 'arrcheck' CLI command.
  2. 2. For arrays running NimbleOS versions < 5.0.10.100: Plan an upgrade to NimbleOS 5.0.10.100 or later.
  3. 3. For arrays running NimbleOS versions 5.1.x: Plan an upgrade to NimbleOS 5.2.1.0 or later.
  4. 4. For arrays running NimbleOS versions 5.2.x < 5.2.1.500: Plan an upgrade to NimbleOS 5.2.1.0 or later.
  5. 5. For arrays running NimbleOS version 5.3.1.0: Plan an upgrade to NimbleOS 6.0.0.100 or later.
  6. 6. Review HPE Nimble Storage upgrade prerequisites and best practices from support.hpe.com before initiating the upgrade.
  7. 7. Schedule a maintenance window as upgrades require array downtime.
  8. 8. Download the appropriate NimbleOS firmware from HPE Support and upload to the array.
Caveat Upgrading NimbleOS requires downtime and should be performed during a planned maintenance window; ensure valid backup exists and review compatibility notes

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

Fix this in Nimbleos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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