Oh no, you're thinking, yet another cookie pop-up. Well, sorry, it's the law. We measure how many people read us, and ensure you see relevant ads, by storing cookies on your device. If you're cool with that, hit “Accept all Cookies”. For more info and to customize your settings, hit “Customize Settings”.

Review and manage your consent

Here's an overview of our use of cookies, similar technologies and how to manage them. You can also change your choices at any time, by hitting the “Your Consent Options” link on the site's footer.

Manage Cookie Preferences
  • These cookies are strictly necessary so that you can navigate the site as normal and use all features. Without these cookies we cannot provide you with the service that you expect.

  • These cookies are used to make advertising messages more relevant to you. They perform functions like preventing the same ad from continuously reappearing, ensuring that ads are properly displayed for advertisers, and in some cases selecting advertisements that are based on your interests.

  • These cookies collect information in aggregate form to help us understand how our websites are being used. They allow us to count visits and traffic sources so that we can measure and improve the performance of our sites. If people say no to these cookies, we do not know how many people have visited and we cannot monitor performance.

See also our Cookie policy and Privacy policy.

This article is more than 1 year old

Asterisk users need to patch DoS bug

Overlap dialling lets attacker shut down system

Asterisk users need to get busy with a patch.

In September, the popular open-source IP PBX project advised users to switch off its “overlap dialling” feature to dodge a possible denial-of-service (DoS) vulnerability.

Overlap dialling is designed to reduce call setup time, by letting the system start looking for destinations from an incomplete number.

The original bug report explained: “If this functionality is used with a device that has performed username/password authentication, RTP resources are leaked. This occurs because the code fails to release the old RTP resources before allocating new ones in this scenario. If all resources are used then RTP port exhaustion will occur and no RTP sessions are able to be set up.”

The original advice carried an upgrade recommendation, but said disabling overlap dialling offered a workaround – however, the workaround didn't work.

“It has been brought to our attention by Walter Doekes that this same leak can be exploited without the use of the overlap dialling feature. Sending SIP requests in a specific sequence outside the norm could also cause the leak of RTP resources. By sending an in-dialog INVITE after receiving a 404 response (but before sending an ACK), an attacker could cause the same leak to occur,” the updated advisory says.

The bug affects Asterisk Open Source versions 11.x, 13.x, and Certified Asterisk 11.6 and 13.8, all of which need to be upgraded. ®

Similar topics

TIP US OFF

Send us news


Other stories you might like