dbcve.org
OpenshiftApplication · Redhat

CVE-2022-3262

HIGH · 8.1 CVSS v3.1 Published 2022-12-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
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 flaw was found in Openshift. A pod with a DNSPolicy of "ClusterFirst" may incorrectly resolve the hostname based on a service provided. This flaw allows an attacker to supply an incorrect name with the DNS search policy, affecting confidentiality and availability.

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, a pod configured with DNSPolicy 'ClusterFirst' can incorrectly resolve hostnames due to a flaw in how the DNS search policy handles service-provided names. An attacker who can influence or supply hostname information can cause the pod to resolve to incorrect IP addresses, potentially redirecting traffic or causing denial of service.

MitigationReview and restrict pod DNS policies, implement network policies to limit DNS manipulation, and apply available OpenShift patches. Consider using DNSPolicy 'ClusterFirstWithHostNet' or 'Default' where appropriate, and validate DNS resolution results.

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
OpenshiftApplication
Affected:= 4.9

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 OpenShift version
    Run 'oc version' or check the cluster version with 'oc get clusterversion -o jsonpath='{.items[0].status.desired.version}''
    Affected if The version equals 4.9 - any pod using ClusterFirst DNS policy in this version is potentially affected
  2. List pods with ClusterFirst DNSPolicy
    Run 'oc get pods --all-namespaces -o jsonpath='{range .items[*]}{.metadata.namespace}{.metadata.name}{.spec.dnsPolicy}{"\n"}{end}'' and look for pods with 'ClusterFirst' policy (note: ClusterFirst is the default if no dnsPolicy is specified)
    Affected if Any pod using ClusterFirst DNSPolicy (which is the default) in an affected OpenShift 4.9 cluster
  3. Verify DNS configuration in namespace
    Check for pods in namespaces where DNS services are managed by the cluster by inspecting pod specs with 'oc get pod -o yaml' and examining the dnsPolicy field
    Affected if Pods have dnsPolicy set to 'ClusterFirst' and rely on cluster DNS for service name resolution
  4. Confirm service discovery usage
    Review pod configurations for references to Kubernetes service names (e.g., via environment variables like <SERVICE>_SERVICE_HOST or in application code connecting to service names) using 'oc describe pod <podname>'
    Affected if Pods use Kubernetes service names for internal communication and resolve them via cluster DNS

If OpenShift version is exactly 4.9 AND pods are using the default ClusterFirst DNS policy with service-based hostname resolution, the environment is affected by this CVE.

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 restrict pod DNS policies, implement network policies to limit DNS manipulation, and apply available OpenShift patches. Consider using DNSPolicy 'ClusterFirstWithHostNet' or 'Default' where appropriate, and validate DNS resolution results.

Recommended fix Moderate confidence

OpenShift 4.10 or later (refer to Red Hat bugzilla for exact fixed version)

  1. 1. Verify the current OpenShift cluster version using 'oc get clusterversion'
  2. 2. Plan a maintenance window for the cluster upgrade
  3. 3. Follow the OpenShift upgrade documentation to upgrade to version 4.10 or later
  4. 4. After upgrade, verify the cluster is healthy using 'oc get nodes' and 'oc get clusterversion'
  5. 5. Test DNS resolution for pods with ClusterFirst DNSPolicy to confirm the vulnerability is remediated
Caveat Upgrade may require cluster downtime; review OpenShift upgrade notes for potential compatibility issues

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

Fix this in Openshift Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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