Unauthorized cluster access through race condition
Published Apr 22, 2025 · Updated Apr 25, 2025
Race condition in HPE Cray Data Virtualization Service before COS Base 3.2.0 allows attackers to gain unauthorized cluster access. HPE has not published the affected function or the shared-resource operation that lacks synchronization in the DVS client. Exploitation requires an adjacent Cray cluster position, a susceptible configuration, and winning the race; successful access crosses local or cluster controls without reported service interruption.
Summary
What happened
Race condition in HPE Cray Data Virtualization Service before COS Base 3.2.0 allows attackers to gain unauthorized cluster access. HPE has not published the affected function or the shared-resource operation that lacks synchronization in the DVS client. Exploitation requires an adjacent Cray cluster position, a susceptible configuration, and winning the race; successful access crosses local or cluster controls without reported service interruption.
The record
- CVE
- CVE-2025-37088
- Published
- Apr 22, 2025
- Updated
- Apr 25, 2025
- Vendor
- Hewlett Packard Enterprise (HPE)
- Product
- HPE Cray Data Virtualization Service (DVS)
- Classifications
- CWE-362
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 22, 2025CVE publishedPublication date reported by the CVE source.
- Apr 25, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <COS Base 3.2.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo