CVE-2019-11245
Published: 29 August 2019
In kubelet v1.13.6 and v1.14.2, containers for pods that do not specify an explicit runAsUser attempt to run as uid 0 (root) on container restart, or if the image was previously pulled to the node. If the pod specified mustRunAsNonRoot: true, the kubelet will refuse to start the container as root. If the pod did not specify mustRunAsNonRoot: true, the kubelet will run the container as uid 0.
Priority
Status
| Package | Release | Status |
|---|---|---|
|
kubernetes Launchpad, Ubuntu, Debian |
bionic |
Does not exist
|
| cosmic |
Not vulnerable
(code not present)
|
|
| disco |
Not vulnerable
(code not present)
|
|
| trusty |
Does not exist
|
|
| upstream |
Not vulnerable
(debian: Vulnerable code not present)
|
|
| xenial |
Does not exist
|
Severity score breakdown
| Parameter | Value |
|---|---|
| Base score | 7.8 |
| Attack vector | Local |
| Attack complexity | Low |
| Privileges required | Low |
| User interaction | None |
| Scope | Unchanged |
| Confidentiality | High |
| Integrity impact | High |
| Availability impact | High |
| Vector | CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |