Unauthenticated RAID modification via Redfish access
Published Jan 8, 2024 · Updated Jun 18, 2025
Improper access control in Microchip maxView Storage Manager 3.00.23484 through 4.14.00.26064 allows remote attackers to alter RAID data. Microchip identifies the Redfish server as the affected locus but has not disclosed which request path or authorization check fails. The Redfish service must be configured for remote management; successful access permits RAID changes and targeted system-file reads.
Summary
What happened
Improper access control in Microchip maxView Storage Manager 3.00.23484 through 4.14.00.26064 allows remote attackers to alter RAID data. Microchip identifies the Redfish server as the affected locus but has not disclosed which request path or authorization check fails. The Redfish service must be configured for remote management; successful access permits RAID changes and targeted system-file reads.
The record
- CVE
- CVE-2024-22216
- Published
- Jan 8, 2024
- Updated
- Jun 18, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-284, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 8, 2024CVE publishedPublication date reported by the CVE source.
- Jun 18, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo