dbcve.org
Advanced Cluster Management For KubernetesApplication · Redhat

CVE-2022-3248

HIGH · 7.5 CVSS v3.1 Published 2023-10-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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 flaw was found in OpenShift API, as admission checks do not enforce "custom-host" permissions. This issue could allow an attacker to violate the boundaries, as permissions will not be applied.

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

In OpenShift, admission checks fail to properly enforce 'custom-host' permissions, allowing attackers to bypass permission boundaries and potentially access resources outside their intended scope. This is a privilege escalation vulnerability where the admission controller does not correctly validate custom-host related permissions.

MitigationReview and enforce custom-host permission checks in OpenShift admission webhooks; apply any available vendor patches for OpenShift that address this permission enforcement gap.

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
Openshift Container PlatformApplication
Affected:= 4.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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

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

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 OpenShift version
    Run 'oc get clusterversion' or 'oc version' to identify the installed OpenShift Container Platform version
    Affected if The installed version falls within the affected range (4.0 series or specific 4.x versions)
  2. Identify admission webhooks
    Run 'oc get admissionwebhooks.configuration.openshift.io --all-namespaces' to list all admission webhook configurations in the cluster
    Affected if Any admission webhooks are present and processing custom-host related requests
  3. Check for custom-host permission bindings
    Examine RoleBindings and ClusterRoleBindings using 'oc get rolebindings --all-namespaces -o yaml' and 'oc get clusterrolebindings -o yaml', searching for any rules referencing 'custom-host' or host network/host path permissions
    Affected if Custom-host related permissions or host network privileges are granted to users or service accounts beyond cluster-admin
  4. Review admission webhook rules
    Inspect the rules defined in admission webhook configurations via 'oc get validatingwebhookconfigurations' and 'oc get mutatingwebhookconfigurations' to identify any that handle custom-host or host resource operations
    Affected if Admission webhooks allow custom-host or host path operations without proper permission validation
  5. Verify privilege escalation paths
    Check for users with elevated permissions using 'oc auth can-i --list --as=<username>' for host network or host path access, particularly for non-admin users
    Affected if Non-cluster-admin users can access host network or host path resources through the admission controller

A user is affected if running an affected OpenShift version with admission webhooks that handle custom-host permissions without proper enforcement of permission boundaries.

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

Review and enforce custom-host permission checks in OpenShift admission webhooks; apply any available vendor patches for OpenShift that address this permission enforcement gap.

Recommended fix Moderate confidence

Advanced Cluster Management for Kubernetes: upgrade to latest 2.x or 2.x+ release that includes the fix; OpenShift Container Platform: upgrade to a 4.y version (y > 0) that includes the fix per Red Hat security advisory

  1. Contact Red Hat customer support or access the Red Hat Customer Portal to obtain the specific security advisory for CVE-2022-3248
  2. Review the Red Hat Security Advisory (RHSA) associated with this CVE to identify the exact fixed package versions
  3. Upgrade Advanced Cluster Management for Kubernetes to a version newer than 2.0 that includes the security fix
  4. Upgrade OpenShift Container Platform to a version newer than 4.0 that includes the security fix
  5. After upgrading, verify that the custom-host permission checks are now properly enforced in the admission controllers
Caveat Review Red Hat release notes for the target version for any breaking changes or known issues before upgrading production clusters

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

Fix this in Advanced Cluster Management For Kubernetes Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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