Related Articles
All Mix →
Hack My Career: Saskia Braucher
When Saskia joined the tech world, she didn’t follow the conventional path of computer science degrees or coding boot camps. Instead, her journey was shaped…
Why You’re Doing Pentesting Wrong (And 2 Ways to Fix It)
Table of Contents Problem 1: Pententers Are Inexperienced Problem 2: Pentesting Is Too Checklist-Driven Problem 3: Limited Pool of Talent Problem 4: Slow Time To…
How I See Class | Daniel Miessler
I recently read perhaps the best book ever written on the American class system, and it set me to thinking quite a bit about the…
Why Sunlight by Itself Won’t Work Against Nick Fuentes
Nick Fuentes is becoming not only popular, but pretty close to mainstream. He’s been called lots of things, but he says himself he’s a far-right,…
[tl;dr sec] #190 – Securely Build on AI, CISA Pen Test repo, Joining Google’s Red Team
Table of Contents 🏋️ Our Gym 📣 ChatGPT: The Dos and Don'ts for Your Company’s Security 🤖 📜 In this newsletter… AppSec 📣 AWS Security…
Johannes Karlsmyr, Episerver: “The Detectify portal and the findings are easy to understand, even for non-technical employees”
Episerver is a global software company that connects commerce and digital marketing to help organizations create unique digital experiences for their customers, with measurable business…
Impact
When using
--userns-remap, if the root user in the remapped namespace has access to the host filesystem they can modify files under/var/lib/docker/that cause writing files with extended privileges.Patches
Versions 20.10.3 and 19.03.15 contain patches that prevent privilege escalation from remapped user.
Credits
Maintainers would like to thank Alex Chapman for discovering the vulnerability; @awprice, @nathanburrell, @raulgomis, @chris-walz, @erin-jensby, @BassMatt, @mark-adams, @dbaxa for working on it and Zac Ellis for responsibly disclosing it to security@docker.com