dbcve.org
Hyperic ServerApplication · VMware

CVE-2022-38651

CRITICAL · 9.8 CVSS v3.1 Published 2022-11-12
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
A security filter misconfiguration exists in VMware Hyperic Server 5.8.6. Exploitation of this vulnerability enables a malicious party to bypass some authentication requirements when issuing requests to Hyperic Server. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.

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 security filter misconfiguration in VMware Hyperic Server 5.8.6 allows attackers to bypass authentication requirements when sending requests to the server. This is a critical vulnerability (CVSS 9.8) stemming from incorrect filter rules that fail to properly enforce authentication checks on certain endpoints or request paths.

MitigationSince VMware Hyperic Server is end-of-life and no longer supported, organizations should migrate to a supported solution or implement compensating controls such as network segmentation, web application firewall rules, or external authentication proxies to block unauthenticated access.

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
Hyperic ServerApplication
Affected:= 5.8.6

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. Confirm VMware Hyperic Server installation
    Check if VMware Hyperic Server 5.8.6 is installed on the system by reviewing installed software, running services, or checking for the hyperic server process
    Affected if VMware Hyperic Server version 5.8.6 is present on the system
  2. Identify Hyperic Server web interface
    Locate the Hyperic Server web application by checking common ports (typically 7080, 7443) or reviewing server configuration files for the listen address and port settings
    Affected if The Hyperic Server web interface is accessible over the network
  3. Check filter configuration files
    Examine the security filter or web.xml configuration files in the Hyperic Server deployment for filter mappings that may豁免 certain URL patterns from authentication
    Affected if Filter rules explicitly exclude authentication requirements for certain endpoints or paths
  4. Test endpoint access without credentials
    Send unauthenticated HTTP requests to common Hyperic API endpoints such as /hyperic/jmx-console, /hyperic/api, or other administrative paths
    Affected if Requests to protected endpoints succeed without providing valid authentication credentials

A user is affected if VMware Hyperic Server version 5.8.6 is running and accessible, and unauthenticated requests can reach protected endpoints due to the misconfigured security filter.

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

Since VMware Hyperic Server is end-of-life and no longer supported, organizations should migrate to a supported solution or implement compensating controls such as network segmentation, web application firewall rules, or external authentication proxies to block unauthenticated access.

Recommended fix High confidence
  1. Decommission or isolate the affected VMware Hyperic Server 5.8.6 from the network, as the product is end-of-life and no longer supported by the vendor.
  2. If continued use is absolutely necessary, implement strict network segmentation and firewall rules to limit access to the server.
  3. Consider migrating to a supported alternative solution for hypervisor and infrastructure monitoring.
  4. Monitor for any unauthorized access attempts since the vulnerability allows authentication bypass.

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

Fix this in Hyperic Server Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,940
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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