CVE intelligence and bounded remediation

CVE-2022-28620 — Hpe Slingshot Firmware security vulnerability

Critical CVSS 9.8

A remote authentication bypass vulnerability was discovered in HPE Cray Legacy Shasta System Solutions; HPE Slingshot; and HPE Cray EX supercomputers versions: Prior to node controller firmware associated with HPE Cray EX liquid cooled blades, and all versions of chassis controller firmware associated with HPE Cray EX liquid cooled cabinets prior to 1.6.27/1.5.33/1.4.27; All Slingshot versions prior to 1.7.2; All versions of node controller firmware associated with HPE Cray EX liquid cooled blades, and all versions of chassis controller firmware associated with HPE Cray EX liquid cooled cabinets prior to 1.6.27/1.5.33/1.4.27. HPE has provided a software update to resolve this vulnerability in HPE Cray Legacy Shasta System Solutions, HPE Slingshot, and HPE Cray EX Supercomputers.

Severity
Critical
CVSS
9.8 (3.1)
Published
2022-06-24
CISA KEV
Not currently listed
Ecosystem
operating-system

Affected products

  • hpe / slingshot_firmware
  • hpe / cray_ex_supercomputers_firmware / 1.4.27
  • hpe / cray_ex_supercomputers_firmware / 1.5.33
  • hpe / cray_ex_supercomputers_firmware / 1.6.27
  • hpe / cray_sh_supercomputer_air_cooled_base_system_code_firmware / 1.4.27
  • hpe / cray_sh_supercomputer_air_cooled_base_system_code_firmware / 1.5.33

Showing 6 representative product identities from 13 source matches. Confirm exact affected versions with the linked vendor and NVD evidence.

Matched remediation archetype

Authentication bypass and missing authentication

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Map every affected endpoint and protocol path, including alternate ports, legacy routes, recovery flows, service accounts, and machine-to-machine access.
  • Confirm which deployments enable the affected authentication mode and whether the interface is reachable from untrusted networks.
  • Review session, token, credential, and proxy trust configuration without attempting account takeover.

Remediate safely

  • Apply the supported fix and centralize fail-closed authentication before protected request handling.
  • Remove default or embedded credentials, rotate affected secrets and sessions, and bind authentication decisions to the intended audience and channel.
  • Add negative tests for alternate routes, malformed or absent credentials, recovery flows, and proxy-derived identity.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.