dbcve.org
NimbleosOperating system · Hpe

CVE-2022-23703

HIGH · 7.5 CVSS v3.1 Published 2022-04-12
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 during update. This would potentially allow an attacker to intercept and modify network communication for software updates initiated by the Nimble appliance. The following NimbleOS versions, and all subsequent releases, contain a software fix for this vulnerability: 5.0.10.100, 5.2.1.500, 6.0.0.100

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

During NimbleOS software updates, the appliance initiates network communication to fetch update packages. This vulnerability allows a man-in-the-middle attacker to intercept and modify these update transmissions, potentially injecting malicious code into the update process due to missing or inadequate transport layer security (certificate validation or encryption).

MitigationUpdate NimbleOS to version 5.0.10.100 or later for the 5.0.x branch, 5.2.1.500 or later for the 5.2.x branch, or 6.0.0.100 or later for the 6.0.x branch. Schedule the update during a planned maintenance window following HPE's update procedures.

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. Check installed NimbleOS version
    Access the NimbleOS CLI or GUI and run 'show version' or view the system information page to obtain the current OS version.
    Affected if The installed version is < 5.0.10.100, or >= 5.1.0.0 and < 5.2.1.500, or exactly 5.3.1.0.
  2. Identify NimbleOS branch
    Determine which release branch your version belongs to by examining the first two numbers of the version (e.g., 5.0.x, 5.2.x, 5.3.x, 6.0.x).
    Affected if The branch is 5.0.x and version < 5.0.10.100, OR branch is 5.2.x and version < 5.2.1.500, OR branch is 5.3.x and version = 5.3.1.0.
  3. Verify update feature configuration
    Check the NimbleOS management interface for update-related settings. In the CLI, use 'show update' or view the Update Manager settings in the GUI to see if update checks are enabled.
    Affected if The system has update functionality configured or enabled (automatic or manual update checks).

You are affected if your NimbleOS version falls within the vulnerable ranges AND the system is configured to perform update checks, allowing network communication during the update process.

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

Update NimbleOS to version 5.0.10.100 or later for the 5.0.x branch, 5.2.1.500 or later for the 5.2.x branch, or 6.0.0.100 or later for the 6.0.x branch. Schedule the update during a planned maintenance window following HPE's update procedures.

Recommended fix High confidence

Upgrade to NimbleOS 5.0.10.100, 5.2.1.500, or 6.0.0.100 (or any subsequent release)

  1. Identify the current NimbleOS version running on the HPE Nimble Storage array
  2. Determine the appropriate upgrade path based on current version: if < 5.0.10.100, upgrade to 5.0.10.100 or later; if >= 5.1.0.0 and < 5.2.1.500, upgrade to 5.2.1.500 or later; if = 5.3.1.0, upgrade to 6.0.0.100 or later
  3. Review HPE Nimble Storage upgrade documentation and release notes for the target version
  4. Schedule a maintenance window for the upgrade process
  5. Download the appropriate NimbleOS update package from HPE support.hpe.com
  6. Follow HPE Nimble Storage OS update procedures to apply the upgrade
  7. Verify the upgrade was successful and the system is running the patched version

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

Fix this in Nimbleos Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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