First pass on a blog post about CVE-2019-5736.#12592
First pass on a blog post about CVE-2019-5736.#12592k8s-ci-robot merged 7 commits intokubernetes:masterfrom
Conversation
|
Deploy preview for kubernetes-io-master-staging ready! Built with commit cbb745c https://deploy-preview-12592--kubernetes-io-master-staging.netlify.com |
zparnold
left a comment
There was a problem hiding this comment.
Take a look at my suggestion, I could be off base but just let me know 😄
My mistake deftly caught by @zparnold. Co-Authored-By: coderanger <noah@coderanger.net>
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kbarnard10 The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
|
||
| While full details are still embargoed to give people time to patch, the rough version is that when running a process as root (UID 0) inside a container, that process can exploit a bug in runc to gain root privileges on the host running the container. This then allows them unlimited access to the server as well as any other containers on that server. | ||
|
|
||
| If the process inside the container is either trusted (something you know is not hostile) or is not running as UID 0, then the vulnerability does not apply. It can also be prevented by SELinux, if an appropriate policy has been applied. RedHat Enterprise Linux, CentOS, and Fedora all include appropriate SELinux permissions with their packages and so are believed to be unaffected. |
There was a problem hiding this comment.
The official announcement explicitly calls out that the default Fedora policy is still vulnerable. Any reason to think otherwise?
|
|
||
| #### Google Container Engine (GKE) | ||
|
|
||
| Google has issued a [security bulletin](https://cloud.google.com/kubernetes-engine/docs/security-bulletins#february-11-2019-runc) with more detailed information but in short, if you are using the default GKE node image then you are safe. If you are using an Ubuntu or CoreOS node image then you will need to mitigate or upgrade to an image with a fixed version of runc. |
There was a problem hiding this comment.
Note that GKE does not support running with CoreOS images.
|
@coderanger Thanks for the right up. Would you mind correcting the details I commented on? |
* First pass on a blog post about CVE-2019-5736. * Clarify that k8s is not the problem. * Fix example of pinning to an image hash. My mistake deftly caught by @zparnold. Co-Authored-By: coderanger <noah@coderanger.net> * Add links to the rest of the notices or releases. * Add ways to get more info. * RHEL link for those that don't selinux. * Link to Rancher's back ports.
* First pass on a blog post about CVE-2019-5736. * Clarify that k8s is not the problem. * Fix example of pinning to an image hash. My mistake deftly caught by @zparnold. Co-Authored-By: coderanger <noah@coderanger.net> * Add links to the rest of the notices or releases. * Add ways to get more info. * RHEL link for those that don't selinux. * Link to Rancher's back ports.
* First pass on a blog post about CVE-2019-5736. * Clarify that k8s is not the problem. * Fix example of pinning to an image hash. My mistake deftly caught by @zparnold. Co-Authored-By: coderanger <noah@coderanger.net> * Add links to the rest of the notices or releases. * Add ways to get more info. * RHEL link for those that don't selinux. * Link to Rancher's back ports.
Trying to get info out to Kubernetes users so they have some guidance.