dbcve.org
Superdome Flex FirmwareOperating system · Hpe

CVE-2021-26589

MEDIUM · 6.1 CVSS v3.1 Published 2021-10-19
Fix available
A fix is available. Upgrade to 3.40.106 or later.
See remediation →
68/100
Remediation priority · Elevated
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
A potential security vulnerability has been identified in HPE Superdome Flex Servers. The vulnerability could be remotely exploited to allow Cross Site Scripting (XSS) because the Session Cookie is missing an HttpOnly Attribute. HPE has provided a firmware update to resolve the vulnerability in HPE Superdome Flex Servers.

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

The vulnerability is a missing HttpOnly attribute on session cookies in HPE Superdome Flex Servers. Without the HttpOnly flag, session cookies can be accessed via JavaScript, enabling cross-site scripting (XSS) attacks to steal session credentials.

MitigationApply the HPE firmware update for Superdome Flex Servers to add the HttpOnly attribute to session cookies, preventing XSS-based session hijacking.

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
Superdome Flex FirmwareOperating system
Affected:< 3.40.106
Superdome Flex 280 FirmwareOperating system
Affected:< 3.40.106

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
None

CVSS:3.1/AV:N/AC:L/PR:N/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 Superdome Flex system model
    Access the system management interface or BMC/IPMI to confirm the exact model number is either HPE Superdome Flex or HPE Superdome Flex 280
    Affected if The system is an HPE Superdome Flex or Superdome Flex 280 model
  2. Check firmware version
    Using the HPE iLO or system management interface, navigate to the firmware/information section and record the current firmware version installed
    Affected if Firmware version is below 3.40.106 (for example, 3.30.x, 3.20.x, etc.)
  3. Inspect session cookie headers
    Access the HPE Superdome Flex web management interface, log in, and use browser developer tools (Application/Storage tab) or capture HTTP responses with a tool like curl to view the Set-Cookie headers for session cookies
    Affected if Session cookies (JSESSIONID or similar) are present WITHOUT the HttpOnly flag in the Set-Cookie header
  4. Verify HttpOnly flag via HTTP response
    Capture an HTTP response from the web interface after authentication and examine the Set-Cookie headers for the presence of the HttpOnly attribute
    Affected if The Set-Cookie header for session cookies does not contain the string 'HttpOnly'

A system is affected if it is an HPE Superdome Flex or Superdome Flex 280 running firmware version below 3.40.106 AND the session cookies lack the HttpOnly attribute in their Set-Cookie headers.

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

Apply the HPE firmware update for Superdome Flex Servers to add the HttpOnly attribute to session cookies, preventing XSS-based session hijacking.

Recommended fix High confidence

Firmware version 3.40.106

  1. 1. Back up current firmware configuration according to HPE best practices
  2. 2. Download the firmware update version 3.40.106 or later from support.hpe.com for your specific model (Superdome Flex or Superoome Flex 280)
  3. 3. Verify the integrity of the firmware image using checksums provided by HPE
  4. 4. Apply the firmware update following HPE's documented firmware upgrade procedure for Superdome Flex servers
  5. 5. After update completion, verify the system is operational and the firmware version shows 3.40.106 or later
  6. 6. Validate that the Session Cookie now includes the HttpOnly attribute
Caveat Firmware updates may require downtime; ensure proper change management procedures are followed and coordinate with business stakeholders

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

Fix this in Superdome Flex Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
17.0 hours of engineering $3,020
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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