points by sscaryterry 1 day ago | 0 comments
> This is an issue in the kernel networking stack.
Exactly, its not a firecracker issue. Using firecracker without a jailer is like setting your password to "password".
Exactly, its not a firecracker issue. Using firecracker without a jailer is like setting your password to "password".
[–] tclancy 1 day ago
[–] sscaryterry 1 day ago
[–] tptacek 1 day ago
This is a really good bug and nobody should downplay it.
[–] roughly 1 day ago
Also - re: the jailer, do you have more info on that being popped?
[–] tptacek 14 hours ago
[–] catlifeonmars 1 day ago
> They ran it without a jailer
And you said
> getting code execution behind the jailer is still effectively game-over
So I’m really confused, which is it?
[–] tptacek 1 day ago
[–] stogot 1 day ago
then the breach happens in KVM? Isn’t KVM its own software repo, and firecracker sits on top? How is this firecracker and not a KvM thing
[–] bulk88 20 hours ago
[–] tclancy 1 day ago
[–] tptacek 7 hours ago
[–] zobzu 1 day ago
the truth is there plenty more kvm escapes that will be found.
[–] tptacek 12 hours ago