CVE-2018-1000400
published 2018-05-18CVE-2018-1000400: 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…
PriorityP350high8.8CVSS 3.0
AVNACLPRLUINSUCHIHAH
EPSS
2.08%
79.6th percentile
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.
Affected
1 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| kubernetes | cri-o | < 1.9.0 | 1.9.0 |
CVSS provenance
nvdv3.08.8HIGHCVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvdv2.06.5MEDIUMAV:N/AC:L/Au:S/C:P/I:P/A:P
vendor_redhat8.8HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-339v-9xv2-qg2w: Kubernetes CRI-O version prior to 1
ghsa_unreviewed·2022-05-13
CVE-2018-1000400 [HIGH] CWE-269 GHSA-339v-9xv2-qg2w: Kubernetes CRI-O version prior to 1
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.
Red Hat
cri-o: capabilities are not dropped when switching to a non-root user
vendor_redhat·2018-04-27·CVSS 8.8
CVE-2018-1000400 [HIGH] CWE-270 cri-o: capabilities are not dropped when switching to a non-root user
cri-o: capabilities are not dropped when switching to a non-root user
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.
Package: cri-o (Red Hat OpenShift Container Platform 3.10) - Not affected
Package: cri-o (Red Hat OpenShift Container Platform 3.11) - Not affected
Package: cri-o (Red Hat OpenShift Container Platform 4) - Not affected
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2018-1000400 cri-o: capabilities are not dropped when switching to a non-root user
bugzilla·2018-05-14·CVSS 8.8
CVE-2018-1000400 [HIGH] CVE-2018-1000400 cri-o: capabilities are not dropped when switching to a non-root user
CVE-2018-1000400 cri-o: capabilities are not dropped when switching to a non-root user
A flaw was found in cri-o up to version 1.10.2-dev. Pod workloads fails to drop capabilities when switching to a non-root
user. This allows a non root user to create a pod and start it successfully even when the container needs privileged permissions.
References:
https://bugzilla.redhat.com/show_bug.cgi?id=1572526
Patch:
https://github.com/kubernetes-incubator/cri-o/pull/1544
Discussion:
Created cri-o tracking bugs for this issue:
Affects: fedora-all [bug 1578110]
---
I believe this is fixed in cri-o-1.10.1-1.git728df92.fc27
---
Acknowledgments:
Name: OpenShift team (Red Hat)
---
Can we get some clarification on CVE-2018-1000400 status?
https://access.redhat.com/security/cve/cve-2018-10004
Bugzilla
CVE-2018-1000400 cri-o: capabilities are not dropped when switching to a non-root user [fedora-all]
bugzilla·2018-05-14·CVSS 8.8
CVE-2018-1000400 [HIGH] CVE-2018-1000400 cri-o: capabilities are not dropped when switching to a non-root user [fedora-all]
CVE-2018-1000400 cri-o: capabilities are not dropped when switching to a non-root user [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multi
2018-05-18
Published