Unauthenticated memory corruption via undisclosed input
Published Feb 22, 2023 · Updated Mar 17, 2025
Memory corruption in HPE Serviceguard for Linux before A.12.80.05 allows remote attackers to cause unspecified impact. HPE has not published the affected component, the input that reaches it, or the memory operation that corrupts data outside its intended bounds. Network access without authentication or user interaction is sufficient, but public evidence does not define whether exploitation causes code execution, data access, or a service crash.
Summary
What happened
Memory corruption in HPE Serviceguard for Linux before A.12.80.05 allows remote attackers to cause unspecified impact. HPE has not published the affected component, the input that reaches it, or the memory operation that corrupts data outside its intended bounds. Network access without authentication or user interaction is sufficient, but public evidence does not define whether exploitation causes code execution, data access, or a service crash.
The record
- CVE
- CVE-2022-37937
- Published
- Feb 22, 2023
- Updated
- Mar 17, 2025
- Vendor
- Hewlett Packard Enterprise (HPE)
- Product
- HPE Serviceguard for Linux
- Classifications
- CWE-787
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 22, 2023CVE publishedPublication date reported by the CVE source.
- Mar 17, 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 <A.12.80.05
What conditions does exploitation require?
What is affected?
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