How we Rooted Copilot
How we Rooted Copilot
research.eye.security
How we Rooted Copilot - Eye Research
15 comments
-
-
Several years ago I created a Slack bot that ran something like Jupyter notebook in a container, and it would execute Python code that you sent to it and respond with the results. It worked in channels you invited it to as well as private messages, and if you edited your message with your code, it would edit its response to always match the latest input. It was a fun exercise to learn the Slack API, as well as create something non-trivial and marginally useful in that Slack environment. I knew the horrible security implications of such a bot, even with the Python environment containerized, and never considered opening it up outside of my own personal use.
Looks like the AI companies have decided that exact architecture is perfectly safe and secure as long as you obfuscate the input pathway by having to go through a chat-bot. Brilliant.
-
And so Microsoft decided this wasn't a big enough vulnerability to pay them a bounty. Why the fuck would you ever share that with them then, if you could sell it to a black-hat hacking org for thousands?
-
There may not have been any logical progression beyond the container.
-
Surely there wasn't an exploit on the half a year out of date kernel (Article screenshots from April 2025, uname kernel release from a CBL-Mariner released September 3rd 2024).
-
-
-
I'm sure nothing will go wrong with tons of critical business documents being routed through copilot for organizations...
15 comments
$10 says they haven't actually escaped anything and it's just hallucinating a directory structure & file contents
MS said they fixed it and categorised it as a "moderate severity vulnerability" so presumably they did in fact gain root access to the container
If they gained root access to the container, that's not a moderate vulnerability. Root inside a container is still root. You can still access the kernel with root privs and it's the same kernel as the host.
Docker is not a virtual machine.
Even if it had access to its own source during training, the chances of it regurgitating it with total fidelity are zero.