4 ms·
Has anyone been able to reproduce this? Or find a report from someone who could? The exploit depends on the user’s router having enabled a broken ALG implement
by PragmaticPulp 6y ago
Has anyone been able to reproduce this? Or find a report from someone who could?
The exploit depends on the user’s router having enabled a broken ALG implementation that ignores the fragment offset. I’m sure there are routers in the wild with this bug, but so far I haven’t been able to find any reports of the POC exploit working for anyone who tried it (before it was disabled).
The POC shows a message about ALG not being enabled when it fails.
Samy says he used a Netgear R7000. Would be interesting to get some POC test results from other routers.
- arpa 6y agoIt's a router released in 2013 and uses kernel from 2011. I wonder how modern alternative / opensource firmware would compare.
- Dahoon 6y agoWell, for one OpenWRT is on kernel 5.4.
- new23d 6y agoIf one were to calculate the CVSS score or such for this, it would be pretty low.
- gnfargbl 6y agoThe attack relies on the ALG ignoring the IP fragment offset in the UDP case only. In the TCP case, he's splitting up packets by forcing a smaller MSS rather than by relying on IP fragmentation. The IP fragment offset for the attack packet, in the TCP case, will be zero as usual. To detect the attack in the TCP case, the ALG would have to keep a stateful record of the initial sequence number on the outgoing SYN, and to accept the SIP REGISTER packet iff seq# == ISN+1. Because home router firmware is invariably written by the lowest bidder, I would be surprised if very many firmwares actually do that.