dbcve.org
Advanced Cluster Management For KubernetesApplication · Redhat

CVE-2022-3841

HIGH · 7.8 CVSS v3.1 Published 2023-01-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
RHACM: unauthenticated SSRF in console API endpoint. A Server-Side Request Forgery (SSRF) vulnerability was found in the console API endpoint from Red Hat Advanced Cluster Management for Kubernetes (RHACM). An attacker could take advantage of this as the console API endpoint is missing an authentication check, allowing unauthenticated users making requests.

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 · high confidence

A Server-Side Request Forgery (SSRF) vulnerability exists in the console API endpoint of Red Hat Advanced Cluster Management for Kubernetes (RHACM). The console API endpoint lacks authentication validation, allowing unauthenticated attackers to make requests and potentially interact with internal services or exfiltrate data.

MitigationImplement authentication enforcement on the console API endpoint to ensure all requests are validated before processing. Restrict network access to internal resources to prevent potential SSRF exploitation.

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

CVSS:3.1/AV:L/AC:L/PR:L/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 RHACM deployment
    Identify whether Red Hat Advanced Cluster Management for Kubernetes is installed in the cluster, typically by checking for the RHACM operator in the openshift-operators or dedicated namespace, or by querying oc get clusters -A for managed clusters
    Affected if RHACM is deployed and the version is 2.0
  2. Verify RHACM version
    Check the installed RHACM version by querying the operator subscription or the CSV (ClusterServiceVersion) resource: oc get csv -A | grep advanced-cluster-management or check the packagemanifest for RHACM
    Affected if The installed version is exactly 2.0 (the only affected version listed)
  3. Identify console API endpoint exposure
    Determine if the RHACM console API endpoint is network-accessible. Check the route or ingress resource for the RHACM console: oc get routes -A | grep -i console or oc get ingress -A | grep -i rhacm
    Affected if The console API endpoint is exposed to untrusted networks or the public internet
  4. Test console API authentication
    Send an unauthenticated request to the console API endpoint (typically at /api/ or /console/api/) and verify whether the request is rejected or accepted without credentials
    Affected if The console API endpoint accepts and processes requests without requiring authentication credentials
  5. Review network policies
    Check if network policies or firewall rules restrict access from the RHACM components to internal services and metadata endpoints: oc get networkpolicies -A
    Affected if Network policies are absent or permissive, allowing the console API to reach internal cluster services

A user is affected if RHACM version 2.0 is deployed, the console API endpoint is network-accessible, and the endpoint processes requests without authentication enforcement.

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 authentication enforcement on the console API endpoint to ensure all requests are validated before processing. Restrict network access to internal resources to prevent potential SSRF exploitation.

Fix this in Advanced Cluster Management For Kubernetes Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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