Out-of-bounds write in systemd-resolved with crafted TCP payload

I misparsed this as "A bug regarding an OOB write in systemd has been resolved by deployment of a crafted TCP payload" and was hoping for a legendary tale of deeply grey-hat infrastructure hack-patching.

Remind me, why are such critical system components as systemd are still being written in a memory unsafe language?

previously: <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=14652787" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=14652787</a> (5 days ago, 192 points, 237 comments)

Sorry, but this is not a standard TCP payload. I think the bug is in the library that made the packet, not with systemd. They should fix their library.

<i>&quot;A patch to resolve this has been provided...&quot;</i><p>The patch resolves the resolver. Heh.

OT, but I wonder why Poettering chose Kay Sievers to work on systemd in the first place.