CVE-2022-37939
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 · uneditedA potential security vulnerability has been identified in HPE Superdome Flex and Superdome Flex 280 servers. The vulnerability could be locally exploited to allow disclosure of information. HPE has made the following software to resolve the vulnerability in HPE Superdome Flex Servers v3.65.8 and Superdome Flex 280 Servers v1.45.8.
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 confidenceA local information disclosure vulnerability in HPE Superdome Flex and Superdome Flex 280 servers. The vulnerability allows a local attacker to potentially access sensitive information. This is a local-only exploit requiring some level of access to the system.
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< 1.45.8< 3.65.8CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify server modelCheck if the system is an HPE Superdome Flex or Superdome Flex 280 server. This can be done via iLO web interface, iLO REST API, or physical system label.Affected if The system is not a Superdome Flex or Superdome Flex 280 server (not affected)
-
Access iLO management interfaceLog into the HPE iLO web interface or use iLO REST API (https://<ilo-ip>/redfish/v1/) to access server management information. The iLO credential is typically required.Affected if Unable to access iLO interface - local verification may require physical access or existing admin credentials
-
Retrieve current firmware versionNavigate to the iLO web interface: Overview > Server Information > Firmware Version. Alternatively, use Redfish: GET /redfish/v1/Managers/Self or /redfish/v1/Systems/1. Look for the System ROM or iLO firmware version field.Affected if Firmware version cannot be retrieved from the management interface
-
Compare firmware version against affected rangesFor Superdome Flex 280: compare your System ROM version to 1.45.8 (affected if < 1.45.8). For Superdome Flex: compare to 3.65.8 (affected if < 3.65.8). Note the exact version string from the iLO or Redfish output.Affected if Installed firmware version is below 1.45.8 for Superdome Flex 280, or below 3.65.8 for Superdome Flex
-
Verify local access exposureDetermine if untrusted local users or processes have access to the system. Check for shared local accounts, console access, or virtual machine escape paths. Review system logs for unauthorized local access attempts.Affected if Untrusted local users can access the server and the firmware version is in the affected range
A system is affected if it is an HPE Superdome Flex (firmware < 3.65.8) or Superdome Flex 280 (firmware < 1.45.8) server, and an attacker can gain local access to the system.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.45.83.65.8
Apply HPE vendor software updates: upgrade HPE Superdome Flex Servers to v3.65.8 and Superdome Flex 280 Servers to v1.45.8 or later.
Superdome Flex Server: upgrade to firmware v3.65.8; Superdome Flex 280 Server: upgrade to firmware v1.45.8
- Obtain the fixed firmware version from HPE support: v3.65.8 for Superdome Flex Servers or v1.45.8 for Superdome Flex 280 Servers
- Download the firmware update package from support.hpe.com
- Review HPE firmware update documentation for your specific server model
- Apply the firmware update using the HPE iLO management interface or HPE SUM (Smart Update Manager)
- Verify the firmware version has been successfully updated after reboot
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-37939 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-37939 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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