CVE-2018-1000400 json
Kubernetes CRI-O version prior to 1.9 contains a Privilege Context Switching Error (CWE-270) vulnerability in the handling of ambient capab…
published 8y ago modified 4mo ago also EUVD-2018-1897
- cvss
- 8.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.0%
- EPSS 2.0% chance of exploitation in 30 days, percentile 80%
- public exploits
- 0
- none known
Summary
Kubernetes CRI-O version prior to 1.9 contains a Privilege Context Switching Error (CWE-270) vulnerability in the handling of ambient capabilities that can result in containers running with elevated privileges, allowing users abilities they should not have. This attack appears to be exploitable via container execution. This vulnerability appears to have been fixed in 1.9.
Patch / fix
- kubernetes cri-o 1.9.0
- cri-o openshift 3.9 1.9.12-1.gitfa11beb.el7
- cri-tools openshift 3.9 1.0.0-5.rhaos3.9.git8e6013a.el7
- atomic-openshift openshift 3.9 3.9.30-1.git.0.dec1ba7.el7
- openshift-ansible openshift 3.9 3.9.30-1.git.7.46f8678.el7
- atomic-openshift-pod openshift 3.9 3.9.30-1.git.0.dec1ba7.el7
- atomic-openshift-node openshift 3.9 3.9.30-1.git.0.dec1ba7.el7
- atomic-openshift-tests openshift 3.9 3.9.30-1.git.0.dec1ba7.el7
- atomic-openshift-utils openshift 3.9 3.9.30-1.git.7.46f8678.el7
red hat advisories RHBA-2018:1796
- github.com/kubernetes-incubator/cri-o#1558 pull request
Is CVE-2018-1000400 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2018-1000400 updated cvss 4.3
cri-o: capabilities are not dropped when switching to a non-root user
-
Red Hat OpenShift Container Platform 3.9 cri-o 1.9.12-1.gitfa11beb.el7, cri-tools 1.0.0-5.rhaos3.9.git8e6013a.el7, atomic-openshift 3.9.30-1.git.0.dec1ba7.el7, openshift-ansible 3.9.30-1.git.7.46f8678.el7, atomic-openshift-pod 3.9.30-1.git.0.dec1ba7.el7, atomic-openshift-node 3.9.30-1.git.0.dec1ba7.el7, +20 morefixed: vendor fix RHBA-2018:1796
-
Red Hat OpenShift Container Platform 3.10 cri-o Red Hat OpenShift Container Platform 3.11 cri-o Red Hat OpenShift Container Platform 4 cri-onot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
1.97% chance of exploitation in the next 30 days, higher than 80% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.5 | AV:N/AC:L/Au:S/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-269 Improper Privilege Management
References
-
github.com
/kubernetes-incubator/cri-o/pull/1558/files
patch, third-party-advisory
-
securityfocus.com
/bid/104262
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2018-1000400
- NVD CVE-2018-1000400
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.