dbcve.org
Msa 1060 Storage FirmwareOperating system · Hpe

CVE-2023-30910

MEDIUM · 5.4 CVSS v3.1 Published 2023-10-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
HPE MSA Controller prior to version IN210R004 could be remotely exploited to allow inconsistent interpretation of HTTP requests. 

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

This is an HTTP Request Smuggling vulnerability in HPE MSA (Modular Smart Array) Controllers. The flaw allows remote attackers to exploit inconsistent interpretation of HTTP requests between the controller's front-end and back-end components, potentially bypassing security controls or smuggling malicious requests through the system.

MitigationUpgrade HPE MSA Controller firmware to version IN210R004 or later. If immediate upgrading is not possible, implement additional HTTP parsing controls and monitor for anomalous HTTP traffic patterns.

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
Msa 1060 Storage FirmwareOperating system
Affected:< in210r004
Msa 2060 Storage FirmwareOperating system
Affected:< in210r004
Msa 2062 Storage FirmwareOperating system
Affected:< in210r004

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 HPE MSA controller model
    Access the MSA management interface (web UI or CLI) and locate the product model information. The affected models are MSA 1060, MSA 2060, and MSA 2062.
    Affected if The installed device is NOT one of these three models - the vulnerability does not apply.
  2. Check installed firmware version
    In the MSA management web interface, navigate to the Settings or About section to view the firmware version. Alternatively, use the CLI command: 'show firmware-version' or 'show controller' to retrieve version information.
    Affected if The firmware version is older than IN210R004 (e.g., IN210r003, IN210r002, etc.) - the device is potentially affected.
  3. Verify HTTP management interface is enabled
    Check the MSA network settings to confirm the HTTP or HTTPS management interface is enabled and accessible. This is typically found under Network Settings or Access settings in the management UI.
    Affected if HTTP/HTTPS management is enabled and the device has network access - the vulnerability can be exploited.
  4. Confirm management interface is network reachable
    Verify the MSA controller management IP is accessible from network segments. Use ping or port scanning to confirm TCP ports 80/443 are reachable.
    Affected if The management interface is exposed to network traffic - an attacker could potentially exploit the HTTP smuggling flaw.

A user is affected if they have an HPE MSA 1060, 2060, or 2062 controller running firmware version earlier than IN210R004 with the HTTP management interface enabled and network-accessible.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade HPE MSA Controller firmware to version IN210R004 or later. If immediate upgrading is not possible, implement additional HTTP parsing controls and monitor for anomalous HTTP traffic patterns.

Recommended fix High confidence

IN210r004

  1. 1. Identify current firmware version on HPE MSA 1060/2060/2062 controller by accessing the storage system management interface
  2. 2. Navigate to HPE support website (support.hpe.com) and search for your MSA model
  3. 3. Download firmware version IN210r004 or later for your specific MSA model
  4. 4. Review HPE MSA firmware upgrade documentation for prerequisites and procedures
  5. 5. Apply firmware update following HPE's recommended upgrade procedure, typically via the management interface or CLI
  6. 6. Verify the firmware version has been successfully updated to IN210r004 or later
Caveat Firmware updates may require system downtime; verify backup and proper shutdown procedures before applying

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

Fix this in Msa 1060 Storage Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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