Oriel — AI & technology worth noticing, every day.

Firecracker VM Escape: PwnEscape Part 2

Web page · https://pwn.ai/blog/firecracker-escape

First seen by Oriel on .

AI summary

This PwnEscape Part 2 write-up demonstrates escaping a Firecracker microVM by modifying a live vCPU thread’s saved KVM registers, achieving controlled root execution in the host process.

  • The guest used a host-memory primitive to resolve its page through EPT, recover Firecracker’s page tables and load bias, and locate the active vCPU’s pt_regs frame.
  • Validated register, stack, syscall, and code signatures identified the thread returning from KVM_RUN and enabled control-flow redirection without relying on a fixed address.
  • The exploit made Firecracker call its write wrapper with a stack-resident marker, then used xor eax,eax; ret to restore the original KVM_RUN return path.
  • Firecracker emitted exactly eight marker bytes, remained alive with SSH responsive, and passed post-execution checks showing all three temporary stack words were restored.
  • The demonstration targeted Firecracker v1.16.1 running as root without jailer; deployments using privilege dropping, namespaces, and seccomp require separate assessment.

#firecracker #kvm #virtual machine escape #memory exploitation

Generated by gpt-5.6-sol. Check the original for details.

Metric trends

Last 30 days · Up to 120 recorded samples per source and metric, with reposts kept separate · First and latest retained

Points

Score reported by the source.

  • Hacker News: 287, latest observation ; +279 over observed period since
  • Lobsters: 5, latest observation ; +4 over observed period since

Comments

Comment count reported by the source.

  • Hacker News: 143, latest observation ; +143 over observed period since
  • Lobsters: 0, latest observation ; 0 over observed period since

Aliases

SourceExternal IDURL
Hacker News50397219https://pwn.ai/blog/firecracker-escape Read discussion
Lobsterswzz4u3https://pwn.ai/blog/firecracker-escape Read discussion