Poop2Shell Skip to the fix

Critical, exploited in the wild

Poop2Shell

Your colleague went to the toilet. Their laptop didn't.

A design-level flaw in the human digestive subsystem gives anyone walking past an unlocked, authenticated session with the victim's full privileges. Every human is affected. There is no patch, only a reflex.

Also known as Code Brown. CVE requested; MITRE stopped replying.

you@openspace: poop2shell PoC Toilet vacant
CVSS gauge: needle past the end of the scale, at 11.0 out of 10 0 1 2 3 4 5 6 7 8 9 10 11
11.0CVSS, out of 10
Average attack window
7m42s
Exposure window
2.5M yrs
Attack complexity
1 coffee
Patches available
0

Summary

The user process homo_sapiens is periodically preempted by a non-maskable interrupt raised in the lower GI tract. Its handler forces the user to abandon the workstation at once and skips the session-lock routine. The user always locks the toilet door; almost never the computer.

The session stays authenticated and unattended for 7 minutes 42 seconds on average. Any adjacent attacker (colleague, intern, auditor, cat) gets an interactive shell with the victim's privileges. No credentials, no tooling, no skill. Just patience.

The interrupt can be triggered remotely and reliably. A third espresso, or posting “free chili in the kitchen” on the team channel, is enough.

CVSS:4.0/AV:P/AC:L/PR:N/UI:R(urgent)/S:C/C:H/I:H/A:💩

Attack chain

  1. Coffee ingested
  2. Peristalsis
  3. Interrupt raised
  4. Victim sprints, no lock
  5. Attacker sits down
  6. Shell

Exploitation steps

  1. Wait.
  2. Keep waiting. Optionally, offer the target a coffee.
  3. Sit down.

There is no step 4.

Affected systems

PlatformStatusNotes
Windows, all versionsVulnerableWin+L has existed for decades. Nobody presses it.
macOS, all versionsVulnerableHot corners are a story you tell yourself.
Linux, all distributionsVulnerableYour screensaver crashed in 2014. You never noticed.
Remote workersVulnerableThreat actors: toddler, partner, cat. Highly persistent.
Wi-Fi smart toiletsVulnerableBidirectional. Telnet exposed on port 2 (number two).
Kubernetes clustersVulnerableSomeone left kubectl open before lunch.
AstronautsPartiallyZero gravity mitigates nothing. It only adds chaos.
CatsNot affectedThey sit on the keyboard instead. Different bug class.
TypewritersNot affectedAir-gapped by design since 1868.

Indicators of compromise

  • An all-staff email from you announcing croissants tomorrow.
  • Your wallpaper is now the CEO. Or a duck. Or the CEO as a duck.
  • Your chat status reads brb, compiling 💩.
  • git log shows a commit titled fix, signed with your key, deleting every test.
  • 40 kg of rubber ducks ordered on your company card, express delivery.
  • Your .bashrc now contains alias ls='sl'.
  • The chair is warm when you come back. High confidence.

Mitigations

Windows WinL

macOS Ctrl⌘Q

Linux SuperL

Do

  • Lock your screen before you stand up. It takes 0.3 seconds and fully remediates. This is, genuinely, the only real fix.
  • Set auto-lock to one minute. Defense in depth for when the interrupt beats your reflexes.
  • Keep your sudo timeout shorter than a coffee break.

Don't

  • Take the laptop with you. Introduces Drop2Bowl: irreversible data loss.
  • Hold it. The vendor escalates unanswered tickets. Fast. In public.
  • Switch to a high-fibre diet. Fewer incidents, more severe ones.
  • Stop eating. Removes the attack surface by denial of service of the host.

Am I vulnerable?

Official self-assessment. Computed in your browser; nothing leaves it (unlike you, apparently).

Awaiting inputTick what applies.

Disclosure timeline

  1. First observed instance of the interrupt. Vendor ships to production without a patch.

  2. Sir John Harington designs a flushing toilet, introducing the flush() primitive.

  3. Alexander Cumming patents the S-shaped trap: the first water-based firewall.

  4. The Xerox Alto, an early personal workstation, enters service. First unattended session presumed shortly after lunch.

  5. Vendor (Mother Nature) notified through the usual channel.

  6. Vendor response: “Works as intended. Drink water.”

  7. Public disclosure, logo and domain name. Press release drafted in a stall.

FAQ

Am I affected?

Do you eat? Then yes.

Is it exploited in the wild?

Every working day around 10:30, shortly after the coffee break, in every open space on Earth. Peaks on Monday mornings.

Can the attacker escalate to root?

Only if you left a sudo session warm. Your sudo timeout is longer than your bathroom break. Do the maths.

Why does a vulnerability need a logo?

Every serious vulnerability has a logo. This one also has a smell.

Is this related to the other *2Shell bugs?

Same family, different attack surface. The others live in software. This one lives in you.

Should I panic?

No. Lock your screen. Then go. In that order.