flawopen.com/インシデント/Baron Samedit
書類審査員には「バックスラッシュがあれば次の1文字をそのまま書き写す」というルールがあります。末尾がバックスラッシュで終わる書類を渡された審査員は、用紙の端を越えて机の上の書類にまでペンを走らせ、他の申請書の許可印を勝手に書き換えてしまいました。
That second point is the durable engineering lesson. The unescaping function was correct given its assumed precondition. The vulnerability lived in the gap between a documented assumption and an unusual call path that violated it. Preconditions enforced by convention rather than by code fail silently, and they fail years later, when whoever knew the convention has moved on.
Privilege escalation flaws are sometimes discounted because they require existing access. That reasoning misreads how intrusions work. Attackers routinely obtain low-privilege access first — a compromised web application process, a stolen SSH key for an unprivileged account, a container breakout, a malicious dependency running in CI. A reliable local root exploit converts that foothold into total control of the host.
In shared environments the effect compounds: on a multi-user build server or a shell host, this bug meant every user was effectively root.
\0 fails the moment any path can step over one.No. That is what made this unusually severe — the overflow occurred during argument processing, before any authorisation decision. Users with no sudo rights whatsoever could exploit it.
This specific failure mode, yes — a bounds-checked language would panic or throw rather than write out of bounds, turning a root exploit into a crash. The logic error of mishandling a trailing escape could still exist; its consequences would be far less severe.