Skip Links

Network World

  • Social Web 
  • Email 
  • Close

Top 14 VoIP vulnerabilities

The new book “Securing VoIP Networks,” the vulnerable side of VoIP
By Ellen Messmer , Network World , 10/01/2007

How are VoIP networks weak and vulnerable to attack and catastrophic failure? Securing VoIP Networks, the new book by Peter Thermos and Ari Takanen, looks at VoIP infrastructure and analyzes its vulnerabilities much as the Open Web Application Security Project did for Web-related vulnerabilities and Mitre did with its Common Weakness Enumeration dictionary for software. And it’s about human failings, too, not just technology problems.

Here are the top VoIP vulnerabilities explained in Securing VoIP Networks:

1. Insufficient verification of data: In VoIP implementations, this can enable man-in the-middle attacks.

2. Execution flaws: Standard databases are typically used as the backbone of VoIP services and registrations. Implementation has to be paranoid in filtering out active content such as SQL queries from user-provided data such as user names, passwords, and Session Initiation Protocol (SIP) URLs. The majority of problems relating to execution flaws result from bad input filtering and insecure programming practices.

3. String/array/pointer manipulation flaws: Malformed packets with unexpected structures and content can exist in any protocol messages, including SIP, H.323, SDP, MGCP, RTP, and SRTP. Most typical malformed messages include buffer-overflow attacks and other boundary-value conditions. The result is that the input given by the attacker is written over other internal memory content, such as registers and pointers, which will let the attacker take full control of the vulnerable process.

Web vulnerabilities

Experts say most Web applications can be hacked. Here are the top ten vulnerabilities that could put your Web site at risk.
  1. Cross site scripting
  2. Injection flaws
  3. Malicious file execution
  4. Insecure direct object reference
  5. Cross site request forgery
  6. Information leakage and improper error handling
  7. Broken authentication and session management
  8. Insecure cryptographic storage
  9. Insecure communications
  10. Failure to restrict URL access

SOURCE: OWASP (the Open Web Application Security Project)

Click to see: Top 10 vulnerabilities list

4. Low resources: Especially in embedded devices, the resources that VoIP implementations can use can be scarce. Low memory and processing capability could make it easy for an attacker to shut down VoIP services in embedded devices.

5. Low bandwidth: The service has to be built so that it will withstand the load even if every caller makes a call at the same time. When the number of subscribers to a VoIP service is low, this is not a big problem. But when a service is intentionally flooded with thousands of bot clients, or when there is an incident that results in a huge load by valid subscribers, the result might be a shutdown of the whole service.

Partner Content
Foundry Networks

The Foundry Enterprise Advantage

Foundry Networks, Inc. (NASDAQ: FDRY) is a leading provider of high-performance enterprise and service provider switching, routing, security and Web traffic management solutions. Foundry's customers include the world's premier ISPs, metro service providers, and enterprises.

For further information on Foundry Networks please click here.

Leveraging the Advantages
of a Multi-vendor Network Strategy

Today's enterprise network provides more than simply a technology infrastructure. It's an enabler for the enterprise, supporting mission critical applications, creating operational efficiencies and increasing productivity gains. Foundry Networks provides the ideal foundation for a multi-vendor network.

Click here to view whitepaper!

Comments (8)
Login
Forgot your account info?

VoIP security has been done better elsewhereBy phon1k on October 12, 2007, 10:43 pmAny references pointers for the rest of us? Or is this some kind of "special" group that one needs a secret handshake to obtain this wisdom? phon1k

Reply | Read entire comment

Unfortunately equatingBy Anonymous on October 9, 2007, 10:08 pmUnfortunately equating synchronous (i.e. realtime apps. such as VoIP/video) with asynchronous communications (i.e. email/IM/web application) creates a false perception...

Reply | Read entire comment

TDM as fallback - NOTBy Anonymous on October 5, 2007, 10:46 amCome on, I have never in my life owned a fixed line phone. I have used cellular only since 1991. Our company also has never (for close to 10 years) had fixed line...

Reply | Read entire comment

VOIP VulnerabilitiesBy Julian on October 5, 2007, 5:19 am13. Lacking fallback system ?? there is a well worked fallback system, the good old TDM system...

Reply | Read entire comment

replace "VoIP" with any other application...By Anonymous on October 3, 2007, 9:42 am...And you've seen this article a hundred times before.

Reply | Read entire comment

View all comments

Add comment
Anonymous comments subject to approval. Register here for member benefits.
Have a NetworkWorld account? Log in here. Register now for a free account.

Videos

rssRss Feed
Get instant email notification when white papers, webcasts, executive guides are added to our library. Stay informed and up-to-date with the latest on IT Technologies with Network World's Resource Alerts.