dbcve.org
StoragegridApplication · Netapp

CVE-2022-23233

HIGH · 7.5 CVSS v3.1 Published 2022-03-04
Fix available
A fix is available. Upgrade to 11.6.0 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
StorageGRID (formerly StorageGRID Webscale) versions prior to 11.6.0 are susceptible to a vulnerability which when successfully exploited could lead to Denial of Service (DoS) of the Local Distribution Router (LDR) service.

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

StorageGRID versions prior to 11.6.0 contain a vulnerability in the Local Distribution Router (LDR) service that can be exploited to cause Denial of Service. The LDR service is a core component handling data distribution within StorageGRID, and successful exploitation renders this service unavailable.

MitigationUpgrade StorageGRID to version 11.6.0 or later. This is the primary remediation as no workarounds are mentioned in the advisory.

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
StoragegridApplication
Affected:< 11.6.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
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Identify if StorageGRID is deployed
    Check for StorageGRID installation through inventory, documentation, or grid management interface access
    Affected if StorageGRID software is present in the environment
  2. Determine installed StorageGRID version
    Access the Grid Management Interface and navigate to the About page, or use the `sudo storagegrid --version` command if available, to retrieve the current software version
    Affected if The installed version is lower than 11.6.0 (e.g., 11.5.x, 11.4.x, etc.)
  3. Verify LDR service is enabled
    Check the Grid Management Interface under Nodes > LDR Service status, or review the node configuration to confirm the Local Distribution Router service is active
    Affected if The LDR service is running and the version is below 11.6.0
  4. Check for service availability
    Monitor the LDR service status through the Grid Management Interface or by attempting to access data throughput metrics via the LDR service endpoints
    Affected if The LDR service becomes unavailable or unresponsive and the version is below 11.6.0

You are affected if StorageGRID is installed with a version lower than 11.6.0 and the LDR service is enabled, as the vulnerability can cause service unavailability.

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

Upgrade StorageGRID to version 11.6.0 or later. This is the primary remediation as no workarounds are mentioned in the advisory.

Recommended fix Moderate confidence

StorageGRID 11.6.0

  1. 1. Identify current StorageGRID version using the Grid Manager or by running 'sudo storagegrid --version' on the primary Admin Node
  2. 2. Review StorageGRID 11.6.0 release notes for upgrade prerequisites and any pre-upgrade requirements
  3. 3. Create a complete backup of the StorageGRID configuration
  4. 4. Schedule a maintenance window as the upgrade will require service downtime for the LDR services
  5. 5. Download StorageGRID 11.6.0 installation files from the NetApp Downloads portal
  6. 6. Follow the standard StorageGRID upgrade procedure: run the upgrade script, monitor progress, and verify all services restart successfully
  7. 7. After upgrade, verify the LDR service is running and the system is healthy using the Grid Manager
Caveat Review 11.6.0 release notes for any configuration or feature changes; standard upgrade precautions apply (backup config, test in staging if possible)

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

Fix this in Storagegrid Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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