dbcve.org
Serviceguard For LinuxApplication · Hpe

CVE-2022-37936

CRITICAL · 9.8 CVSS v3.1 Published 2023-03-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
Unauthenticated Java deserialization vulnerability in Serviceguard Manager

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 confidence

A critical unauthenticated Java deserialization vulnerability exists in Serviceguard Manager that allows remote attackers to execute arbitrary code without credentials. Java deserialization flaws occur when untrusted data is deserialized without proper validation, enabling gadget chain attacks to achieve RCE.

MitigationApply vendor-provided patches immediately; if no patch available, restrict network access to Serviceguard Manager interfaces via firewall and disable the vulnerable deserialization vectors until patched.

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
Serviceguard For LinuxApplication
Affected:< a.12.80.05

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 if HPE Serviceguard For Linux is installed
    Run 'rpm -qa | grep -i serviceguard' or 'dpkg -l | grep -i serviceguard' to list installed Serviceguard packages
    Affected if No Serviceguard packages are found, then this CVE does not apply
  2. Determine the installed version of Serviceguard
    Run 'cmversion' command or check the package version with 'rpm -q <package_name>' or 'dpkg -s <package_name>'
    Affected if The installed version is lower than a.12.80.05 (for example, a.12.70.00, a.12.01.00, etc.)
  3. Confirm Serviceguard Manager component is present
    Check for the Serviceguard Manager web interface by looking for its process or service, typically running on port 20014 by default. Use 'ps aux | grep -i manager' or check network listening ports with 'netstat -tlnp | grep 20014'
    Affected if Serviceguard Manager process is running and listening on network ports, exposing the vulnerable Java deserialization interface
  4. Verify network exposure of the Serviceguard Manager interface
    Review firewall rules and network configuration to determine if the Serviceguard Manager port (default 20014) is accessible from untrusted networks. Check /etc/sysconfig/iptables or use 'ss -tlnp' to see bound addresses
    Affected if The Serviceguard Manager port is bound to 0.0.0.0 or an exposed network interface, allowing remote attackers to reach the vulnerable deserialization endpoint

You are affected if HPE Serviceguard For Linux is installed with a version lower than a.12.80.05 AND the Serviceguard Manager interface is network-accessible.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-provided patches immediately; if no patch available, restrict network access to Serviceguard Manager interfaces via firewall and disable the vulnerable deserialization vectors until patched.

Recommended fix High confidence

Serviceguard for Linux version a.12.80.05 or later

  1. 1. Download Serviceguard for Linux version a.12.80.05 or later from support.hpe.com
  2. 2. Create a complete backup of the current Serviceguard Manager configuration and data
  3. 3. Stop the Serviceguard Manager service on all nodes in the cluster
  4. 4. Install the updated Serviceguard for Linux package (a.12.80.05 or later) on all cluster nodes
  5. 5. Verify the installation completed successfully by checking the installed version
  6. 6. Start the Serviceguard Manager service on all nodes
  7. 7. Verify the cluster is operational and the vulnerability is resolved
Caveat Review HPE Serviceguard release notes for version a.12.80.05 for any configuration or compatibility changes before upgrading

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

Fix this in Serviceguard For Linux Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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