3 ms·
I'm not sure how much has changed in the last 10 years, but when I did lots of VoIP work then, the consensus in many places was "every ALG is broken, start by d
by viraptor 6y ago
I'm not sure how much has changed in the last 10 years, but when I did lots of VoIP work then, the consensus in many places was "every ALG is broken, start by disabling ALG". SIP is complicated in unexpected places and even with the best intentions ALGs broke packets by rewriting wrong parts or making header formats invalid.
But specifically regarding your question, sip looks like http. Same structure / similar response codes. They probably didn't want to write a very strict sip-detector and ended up checking "looks like a verb+destination+ headers? Good enough". Or maybe it's to support http proxies where a http CONNECT session can turn into sip-tcp? (Never seen that in practice, but I guess it's possible)
Or maybe it's just that the alg processing is per-packet, not per-session? Who knows. Just login to your router and turn off ALG. Your SIP phone most likely already knows how to deal with NAT using stun/turn.
- chc4 6y agoIt's not smuggling a SIP session request via HTTP headers - even if it didn't look anything like HTTP it would be vulnerable to this attack, because the controlled fragment is arbitrary binary data from their POST body. The problem is the router's firmware doing detection on each packet without checking that the fragment offset is 0 first.
- viraptor 6y agoI didn't say it relies on http headers. Just made a guess on what alg may be doing. Yeah - it's broken with fragmentation, and possibly in other ways too.
- pixl97 6y agoSIP ALG is just another reason that IPv6 needs to be everywhere. It is a nightmare to deal with.
- _-___________-_ 6y agoMost any real SIP deployment needs to consider users that are behind NATs without ALG anyway, so SIP ALG is basically worthless.