Out-of-bounds write in systemd-resolved with crafted TCP payload
1–10 of 26 posts
Re: Out-of-bounds write in systemd-resolved with crafted TCP payload
#2"A patch to resolve this has been provided..."
The patch resolves the resolver. Heh.
Re: Out-of-bounds write in systemd-resolved with crafted TCP payload
#3Remind me, why are such critical system components as systemd are still being written in a memory unsafe language?
Re: Out-of-bounds write in systemd-resolved with crafted TCP payload
#4Sorry, 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.
Re: Out-of-bounds write in systemd-resolved with crafted TCP payload
#5previously: https://news.ycombinator.com/item?id=14652787 (5 days ago, 192 points, 237 comments)
Re: Out-of-bounds write in systemd-resolved with crafted TCP payload
#6Remind me, why are such critical system components as systemd are still being written in a memory unsafe language?
I'd love to learn Rust by opportunistically implementing parts of the systemd API.
If any Rustafarians start such an effort, please make some noise about it.
Re: Out-of-bounds write in systemd-resolved with crafted TCP payload
#7Sorry, 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.
"A malicious DNS server can exploit this by responding with a specially crafted TCP payload to trick systemd-resolved in to allocating a buffer that's too small, and subsequently write arbitrary data beyond the end of it."
When your program doesn't handle a malformed input, and this leads to a buffer overflow, it's your fault. When this program is something as important as systemd, the problem is even worse.
Re: Out-of-bounds write in systemd-resolved with crafted TCP payload
#8Sorry, 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.
Anything Internet-facing has to accept any kind of packet without crashing, or at least without failing in an exploitable way. That's the bare minimum you-must-be-this-tall entry requirement of security.
Re: Out-of-bounds write in systemd-resolved with crafted TCP payload
#9Sorry, 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.
Anything Internet-facing has to accept any kind of packet without crashing, or at least without failing in an exploitable way. That's the bare minimum you-must-be-this-tall entry requirement of security.
I believe it was a joke about how Lennart Poettering usually responds to bug reports.
Re: Out-of-bounds write in systemd-resolved with crafted TCP payload
#10Remind me, why are such critical system components as systemd are still being written in a memory unsafe language?
Because if it's good enough for OpenBSD, then it's good enough for us.