2 ms·
With SIP you have two popular models. HTTP Digest, which requires an extra round-trip to get a nonce to auth, and going off IP. "Carriers" and most high volume
by MichaelGG 13y ago
With SIP you have two popular models. HTTP Digest, which requires an extra round-trip to get a nonce to auth, and going off IP. "Carriers" and most high volume folks just auth off IP. If you were using SIP TCP only, this wouldn't be so terrible. HTTP Digest is generally only used for phones and the like.
Except, most folks use UDP, and IP auth is simply broken on many SIP platforms. If you can spoof an IP packet (who can't?) and you know someone's IP that's allowed to send traffic, _most likely_ you can auth as them and complete the call and no one will notice. More paranoid implementations will give each customer their own IP and setup firewall rules, which mitigates the issue.
Either way, using UDP and going off IP is still terrible. Because now, a spoofed IP packet comes in, and based on that packet alone, you're going to start up all the call processing and make a call. The SIP transaction might timeout and end the call in 5-60 seconds, but it's very open to [D]DoS'ing. Oh, and even some major platforms consider 100 calls/sec to be "high volume", so even an unsophisticated attacker could probably bring a lot of systems to their knees via IP spoofing.
The real mitigation is that there's so much low hanging fruit, that hackers are just going after the quick buck by hitting PBXes or phones and calling rebate numbers or 30+ cent destinations.
Telephony has traditionally been a trusted system, and a lot of that's carried over to VoIP.