News for hackers. Stuff that matters.
Re:Exploiting the Linux kernel via packet sockets by d33 on Wednesday May 10, 2017 @05:35PM (#14311941)
That's pretty interesting. Does it mean it allows escaping Docker containers if you compromise a service ran as root in it?
Re:Exploiting the Linux kernel via packet sockets by user5994461 on Thursday May 11, 2017 @09:54AM (#14315990)
As a rule of Thumb, an attack can ALWAYS escape from Docker containers.

These containers are a light way to separate processes. They are not intended as a security measure to isolate malicious processes that tries to escape.

Re:Exploiting the Linux kernel via packet sockets by dohqu8Zi on Wednesday May 10, 2017 @05:37PM (#14311957)
No, Docker usually drops CAP_NET_RAW within the container. But you can change that and other container technologies definitely keep CAP_NET_RAW within the container.
Re:Exploiting the Linux kernel via packet sockets by wrongmmmm on Wednesday May 10, 2017 @07:40PM (#14312739)
Not true. CAP_NET_RAW is on by default: https://github.com/moby/moby/blob/master/oci/defaults_linux....

Otherwise no one could ping from a container.

Re:Exploiting the Linux kernel via packet sockets by dohqu8Zi on Thursday May 11, 2017 @03:11AM (#14314319)
Thanks for the correction.
Re:Exploiting the Linux kernel via packet sockets by dohqu8Zi on Wednesday May 10, 2017 @05:40PM (#14311973)
BTW: Depending on the configuration you can create a new namespace within Docker to gain CAP_NET_RAW since namespaces can nest.