Openshift Container PlatformApplication · Redhat
CVE-2020-14336
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 the Restricted Security Context Constraints (SCC), where it allows pods to craft custom network packets. This flaw allows an attacker to cause a denial of service attack on an OpenShift Container Platform cluster if they can deploy pods. The highest threat from this vulnerability is to system 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 confidenceThe Restricted Security Context Constraints (SCC) in OpenShift Container Platform contains a flaw that allows deployed pods to craft custom network packets, enabling network-based denial of service attacks against the cluster. An attacker with pod deployment capabilities can exploit this to impact system availability.
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
Openshift Container PlatformApplication
= 3.11= 4.5.16= 4.6CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check OpenShift Container Platform versionRun 'oc version' or check the cluster version with 'oc get clusterversion'Affected if The installed version is exactly 3.11, 4.5.16, or 4.6
-
Identify the Restricted SCC configurationRun 'oc get scc restricted -o yaml' to view the Security Context Constraint detailsAffected if The SCC allows NET_RAW or similar network capabilities that should be restricted
-
Verify if non-admin users can deploy podsCheck user permissions with 'oc auth can-i create pods' as a non-admin user, or review role bindings with 'oc get rolebindings -o wide'Affected if Non-admin users or service accounts have permissions to create pods in any namespace
-
Inspect NET_RAW capability in pod deploymentsReview running pods with 'oc get pods -o yaml | grep -i capability' to see if NET_RAW is present in security contextsAffected if Pods are running with NET_RAW or similar raw network capabilities enabled
A user is affected if running OpenShift Container Platform version 3.11, 4.5.16, or 4.6 AND the Restricted SCC permits NET_RAW capability AND non-privileged users can deploy pods that could leverage this capability.
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.
From vendor dataReview and restrict SCC permissions for non-admin users, or apply any available OpenShift updates that address this SCC bypass. Limit pod deployment privileges to trusted users only.
Fix this in Openshift Container Platform
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-14336 — 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-2020-14336 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