Post #762831
2026-03-19 11:05 UTC
Replies (10)
-
@kouett@soc.kouett.net.eu.org 2026-03-19 11:20
@sash oof. this one is bad :D
-
@plaindocs@chaos.social 2026-03-19 11:15
@sash ๐ฅ
-
@petrichor@digipres.club 2026-03-19 11:20
@sash Ah, that's why the OpenWRT firmware build service is overloaded! ๐ซ Thanks for your efforts, I'm in awe of those who do this work to help keep the rest of us a little safer.
-
@lunareclipse@snug.moe 2026-03-19 11:23
@sash@hachyderm.io hmmm I really need to update my router huh
-
@BafDyce@chaos.social 2026-03-19 12:14
@sash TIL that this works: This might come in handy in future pentests :)
-
@j_r@social.jugendhacker.de 2026-03-19 12:36
@sash wow looks like a lot of people are upgrading right now, judging by the ASU server stats ๐ซฃ
-
@shadowdancer@mstdn.social 2026-03-19 15:45
@sash Thanks for the heads up! I frequent the forums but it's been a couple of days since my last visit so I missed this one. It seems the release was announced 17h ago. Now, if this was found in a commercial router firmware, how quickly would you guess there'd be a fix available? I'd say weeks, or maybe months. edit: hashtag for better reach #OpenWRT
-
@nicksilkey@hachyderm.io 2026-03-19 16:56
@sash what a find. thanks for sharing, friend. โ๏ธ๐
-
@uvok@woof.tech 2026-03-19 17:28
@sash funny coincidence, I fixed the same class of bug at work recently
-
@dgl@infosec.exchange 2026-03-20 02:07
@sash very cool find! I think it would be possible to fit it (just) in 32 characters with: (That url works; d.cx is serving a hello world alert payload at the moment, it works with e.g. https://d.cx/~dgl/l.html but I haven't tried actually doing it with OpenWRT.)