CVE-2022-0567
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 · uneditedA flaw was found in ovn-kubernetes. This flaw allows a system administrator or privileged attacker to create an egress network policy that bypasses existing ingress policies of other pods in a cluster, allowing network traffic to access pods that should not be reachable. This issue results in information disclosure and other attacks on other pods that should not be reachable.
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 confidenceA flaw in ovn-kubernetes allows privileged attackers to create egress network policies that bypass existing ingress policies on other pods, enabling unauthorized network access to previously isolated pods and resulting in information disclosure.
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< 4.7.47>= 4.8.0, < 4.8.36>= 4.9.0, < 4.9.27>= 4.10.0, < 4.10.8CVSS 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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Determine ovn-kubernetes versionRun 'kubectl get pods -n openshift-ovn-kubernetes -o jsonpath="{.items[0].spec.containers[0].image}"' or check the ovn-kubernetes operator version with 'kubectl get clusterversion -o jsonpath={.status.desired.version}'Affected if The installed version falls within any of these ranges: < 4.7.47, >= 4.8.0 and < 4.8.36, >= 4.9.0 and < 4.9.27, or >= 4.10.0 and < 4.10.8
-
Identify egress network policiesRun 'kubectl get egressnetworkpolicy --all-namespaces' or 'oc get egressnetworkpolicy --all-namespaces' to list all egress network policies in the clusterAffected if Any egress network policies exist in the cluster, as these could be exploited to bypass ingress restrictions on other pods
-
Review egress policy rules for permissivenessDescribe each egress network policy with 'kubectl describe egressnetworkpolicy <name> -n <namespace>' and examine the destination cidrBlocks and dnsName specificationsAffected if Egress policies allow traffic to destinations that should not have access based on your security model, particularly policies targeting pods that should be isolated via ingress rules
You are affected if your ovn-kubernetes version is within the vulnerable ranges listed AND you have egress network policies that could be leveraged to access pods supposedly protected by ingress policies.
Generated from the published advisory. Verify against your own configuration.
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 · scoped4.7.474.8.364.9.27
Upgrade ovn-kubernetes to the patched version and audit existing network policies for any unauthorized or overly permissive egress rules that may have been created.
4.10.8 or later (or 4.7.47/4.8.36/4.9.27 depending on current version branch)
- Identify the current ovn-kubernetes version in the cluster
- Determine which version branch is in use (4.7.x, 4.8.x, 4.9.x, or 4.10.x)
- Plan upgrade to the first fixed version for that branch: 4.7.47, 4.8.36, 4.9.27, or 4.10.8 respectively
- Test the upgrade in a non-production environment before applying to production
- Schedule a maintenance window for the production upgrade
- Perform the upgrade following standard cluster upgrade procedures
- Verify that ovn-kubernetes components are running the patched version after upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-0567 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-0567 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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