SIP is susceptible to the following threats and attacks:
Denial of service – the consequence of a DOS attack is that the entity attacked becomes unavailable. This includes scenarios like targeting a certain UA or proxy and flooding them with requests. Multicast requests are further examples.
Eavesdropping – if messages are sent in clear text, malicious users can eavesdrop and get session information, making it easy for them to launch a variety of hijacking-style attacks.
Tearing down sessions – an attacker can insert messages like a CANCEL request to stop a caller from communicating with someone else. He can also send a BYE request to terminate the session.
Registration hijacking – an attacker can register on a user's behalf and direct all traffic destined to that user towards his own machine.
Session hijacking – an attacker can send an INVITE request within dialog requests to modify requests en route to change session descriptions and direct media elsewhere. A session hijacker can also reply to a caller with a 3xx-class response, thereby redirecting a session establishment request to his own machine.
Impersonating a server – someone else pretends to be the server and forges a response. The original message could be misrouted.
Man in the middle – this attack is where attackers tamper with a message on its way to a recipient.
There are six aspects to the SIP security framework:
Authentication – this is a means of identifying ...