dbcve.org
Powervault Me5012 FirmwareOperating system · Dell

CVE-2023-23691

HIGH · 8.8 CVSS v3.1 Published 2023-01-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Dell EMC PV ME5, versions ME5.1.0.0.0 and ME5.1.0.1.0, contains a Client-side desync Vulnerability. An unauthenticated attacker could potentially exploit this vulnerability to force a victim's browser to desynchronize its connection with the website, typically leading to XSS and DoS.

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

Dell EMC PV ME5 storage systems versions ME5.1.0.0.0 and ME5.1.0.1.0 contain a client-side desync (HTTP request smuggling) vulnerability. An unauthenticated remote attacker can exploit this to desynchronize the victim's browser connection with the website, enabling reflected XSS attacks and causing denial of service conditions.

MitigationApply the vendor-supplied firmware update to a patched version. If no update is available, implement HTTP normalization at upstream proxies/load balancers to detect and block smuggling attempts.

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
Powervault Me5012 FirmwareOperating system
Affected:< me5.1.1.0.5
Powervault Me5024 FirmwareOperating system
Affected:< me5.1.1.0.5
Powervault Me5084 FirmwareOperating system
Affected:< me5.1.1.0.5

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 the storage system model
    Access the device management interface or CLI and retrieve the system model information. Look for Dell Powervault Me5012, Me5024, or Me5084 designations.
    Affected if The device is NOT a Dell Powervault ME5 series model (Me5012, Me5024, or Me5084).
  2. Retrieve the installed firmware version
    Log into the storage system via web UI, CLI (SSH), or management tools and navigate to the firmware or system information section. Note the exact firmware version number displayed.
    Affected if The firmware version is below me5.1.1.0.5 (for example, me5.1.0.0.0 or me5.1.0.1.0).
  3. Verify HTTP management interface accessibility
    Check if the device web management interface (typically on ports 80/443 or custom management ports) is exposed and reachable on the network.
    Affected if The HTTP/HTTPS management interface is accessible and the firmware version is below me5.1.1.0.5.

You are affected if you are running a Dell Powervault Me5012, Me5024, or Me5084 with firmware version below me5.1.1.0.5 and the management interface is 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

Apply the vendor-supplied firmware update to a patched version. If no update is available, implement HTTP normalization at upstream proxies/load balancers to detect and block smuggling attempts.

Recommended fix High confidence

me5.1.1.0.5 or later

  1. 1. Identify the current firmware version of the Powervault ME5 series storage array by accessing the management interface or using the CLI command to display system information
  2. 2. Navigate to the Dell Support website (www.dell.com) and locate the firmware download page for Powervault ME5 series
  3. 3. Download the fixed firmware version me5.1.1.0.5 or later for your specific model (Me5012, Me5024, or Me5084)
  4. 4. Review the firmware upgrade guide and release notes for any prerequisites or specific upgrade procedures
  5. 5. Back up the current storage array configuration according to best practices
  6. 6. Apply the firmware update using the recommended method (via iDRAC, OMSS, or local upgrade)
  7. 7. Verify the firmware version has been successfully updated to me5.1.1.0.5 or later after the process completes

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

Fix this in Powervault Me5012 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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