dbcve.org
Advanced Cluster Management For KubernetesApplication · Redhat

CVE-2022-2238

MEDIUM · 6.5 CVSS v3.1 Published 2022-09-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 vulnerability was found in the search-api container in Red Hat Advanced Cluster Management for Kubernetes when a query in the search filter gets parsed by the backend. This flaw allows an attacker to craft specific strings containing special characters that lead to crashing the pod and affects system availability while restarting.

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 denial-of-service vulnerability exists in the search-api container of Red Hat Advanced Cluster Management for Kubernetes. Attackers can send crafted search queries containing special characters that cause the backend parser to crash, resulting in pod termination and service unavailability until restart completes.

MitigationImplement input validation and sanitization on search filter queries to reject or properly escape special characters before parsing. Consider adding rate limiting on the search API endpoint as a defense-in-depth measure.

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
Advanced Cluster Management For KubernetesApplication
Affected:= 2.0

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 Red Hat Advanced Cluster Management installation
    Run 'oc get pods -n open-cluster-management' or 'kubectl get pods -n open-cluster-management' to list all pods in the open-cluster-management namespace
    Affected if No RHACM pods are found in the open-cluster-management namespace - not affected
  2. Verify the RHACM version
    Run 'oc get multiclusterhub -n open-cluster-management' or check the operator CSV version with 'oc get csv -n open-cluster-management'
    Affected if Version is exactly 2.0 - potentially affected; versions other than 2.0 are not affected by this specific CVE
  3. Check search-api pod status and restart count
    Run 'oc get pods -n open-cluster-management -l app=search-api' to find the search-api pods, then check 'oc describe pod <search-api-pod-name> -n open-cluster-management' for restart count and last state
    Affected if High restart count or recent crash events in pod status indicate the vulnerability may have been exploited
  4. Examine search-api pod logs for parser crashes
    Run 'oc logs <search-api-pod-name> -n open-cluster-management' and search for panic, crash, or parse error patterns related to search queries
    Affected if Logs contain panic messages, parse failures, or unexpected termination related to search query processing
  5. Check for service unavailability indicators
    Test search API availability with 'oc get routes -n open-cluster-management' to find the search API endpoint, then attempt access or check for 5xx errors
    Affected if Search API endpoint returns errors or is unreachable, suggesting possible exploitation

Environment is affected if Red Hat Advanced Cluster Management for Kubernetes version 2.0 is installed with the search-api component running and experiencing crashes or unexpected restarts.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement input validation and sanitization on search filter queries to reject or properly escape special characters before parsing. Consider adding rate limiting on the search API endpoint as a defense-in-depth measure.

Fix this in Advanced Cluster Management For Kubernetes Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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