dbcve.org
Maxview Storage ManagerApplication · Microchip

CVE-2024-22216

CRITICAL · 10.0 CVSS v3.1 Published 2024-01-08
Fix available
A fix is available. Upgrade to after 4.14.00.26064 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
In default installations of Microchip maxView Storage Manager (for Adaptec Smart Storage Controllers) where Redfish server is configured for remote system management, unauthorized access can occur, with data modification and information disclosure. This affects 3.00.23484 through 4.14.00.26064 (except for the patched versions 3.07.23980 and 4.07.00.25339).

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

This is an authorization bypass vulnerability in the Redfish server component of Microchip maxView Storage Manager. In default installations where Redfish is enabled for remote system management, unauthenticated attackers can gain unauthorized access to modify storage configuration data and read sensitive system information.

MitigationUpdate maxView Storage Manager to patched versions 3.07.23980 or 4.07.00.25339. If immediate patching is not possible, restrict network access to the Redfish interface using firewalls or access controls.

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
Maxview Storage ManagerApplication
Affected:>= 3.00.23484, <= 4.14.00.26064

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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. Identify if maxView Storage Manager is installed
    Locate the maxView installation directory or check installed programs list for 'Microchip maxView Storage Manager' or 'maxView'
    Affected if The software is not present on the system, the vulnerability does not apply
  2. Determine the installed version of maxView Storage Manager
    Check the version information in the installation directory, program properties, or use the maxView utility command to query the version
    Affected if The installed version falls outside the range 3.00.23484 to 4.14.00.26064, the vulnerability does not apply
  3. Verify if Redfish service is enabled
    Check the maxView configuration settings or service status to determine whether the Redfish interface is turned on for remote system management
    Affected if Redfish is disabled or not configured, the vulnerability cannot be exploited
  4. Check Redfish network accessibility
    Inspect network configuration, firewall rules, or service bindings to determine if the Redfish service port (typically 5000 or 8443) is exposed to the network
    Affected if Redfish is only accessible from localhost or a trusted internal network, the exploitability is significantly reduced

A user is affected if maxView Storage Manager is installed with a version between 3.00.23484 and 4.14.00.26064 AND the Redfish service is enabled and accessible to potential attackers.

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 a release after 4.14.00.26064
Interim mitigation

Update maxView Storage Manager to patched versions 3.07.23980 or 4.07.00.25339. If immediate patching is not possible, restrict network access to the Redfish interface using firewalls or access controls.

Recommended fix High confidence

Version 3.07.23980 or later for 3.x branch; Version 4.07.00.25339 or later for 4.x branch

  1. 1. Identify the current installed version of MaxView Storage Manager
  2. 2. For version 3.x branch: upgrade to version 3.07.23980 or later
  3. 3. For version 4.x branch: upgrade to version 4.07.00.25339 or later
  4. 4. After upgrade, verify the Redfish server configuration to ensure proper access controls are in place
  5. 5. Test that remote system management functionality works correctly post-upgrade
Caveat Breaking changes not specified in available documentation; test in non-production environment before deploying

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

Fix this in Maxview Storage Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
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,152.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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