top of page
Search
  • Writer's pictureDarren McDonald

rtp-red-cap, RTP Bleed for Poor People

Updated: Apr 12

Intended Audience: penetration testers, other technical cyber security professionals, and VOIP telephony engineers without €10k to spare.


2024-04-12 Update, we have released to tool to exploit this vulnerability without going through quite so many steps. This tool can be found on github, https://github.com/CR-DMcDonald/voipire/ .


RTP sessions can be highjacked from RTP proxies by sending a RTP packet to the right port. rtpnatscan is the only tool I know which does this, sending four packets just containing rtp headers, scanning ports to find and redirect RTP. While rtpnatscan is smart enough to detect the resulting stolen audio stream, theres no way to save or listen to it. But as pentester or security professional you'll want to listen to it so you can figure out if the RTP streams are encrypted or not, which makes a massive difference the severity of the issue.


SIP Vicious Pro, a VOIP testing tool reportedly does allow this, but the price is difficult to justify. At the time of writing the listed price is €800 a month, plus an additional €800 one off mandatory training course. This comes to €10,400 for the first year.


That's a shame, because for a smaller pentesting firms like mine that's just too much money for a tool I'll only use twice a year. To give you some context the most expensive pentesting tool I use costs about £2k pa, and I use it at least weekly.


Looking for other options, I found a way to use the rtpnatscan tool with a script and OSS tools to achieve what I wanted. Specifically I used rtpnatscan, wireshark, python, scapy, and audacity in a hacky, rough process but provides enough evidence to be confident that a system is vulnerable and the RTP streams are unencrypted.


Warning: this attack will disrupt VOIP calls and leak private VOIP calls, use with care and authorisation from the system owner.


Step 1 - Prepare to Capture RTP Traffic


Start wireshark listening on the interface you expect your RTP packets to come in on.


Step 2 - run rtpnatscan against all the ports


./rtpnatscan [target ip address] 16384 32767

The last two numbers are the start and end of the RTP nat port range. By default, RTP proxies use ports between 16384 and 32767, inclusive. If the RTP proxy is vulnerable and there are on going calls using the ports in your range, you'll know you've started to receive RTP streams when you see output lines like this.

received 172 bytes from target port 16422, seq 62975

Wait a few seconds to get a snippet of the stream, press ctrl-c and kill the application. Stop your Wireshark capture, and save the results as a pcapng file.

Step 3 - Strip the RTP Headers and Save the Raw Audio


I've written a scapy python script for this. Usage: .\rtp-red-cap.py [target ip address] [file to pcapng file]. This will spit out one .raw audio file for each rtp stream rtpnatscan found.


You can find a copy of this script released under GPLv3 here.


Step 4 - Playing the Audio File


In order to play the audio files you've just captured, you'll need to figure out the frequency, number of channels, and encoding format. This information is usually contain in the SIP signalling packets, which you don't have.


However, for audio calls 8000 hz, ALAW encoding, and monochannel are a good first guess. You can play this on Linux with ffplay, for example...

ffplay -f alaw -ar 8k -ac 1 audio-36324.raw

Another alternative is to use Audacity. Click File -> Import -> Raw Data.... and select the following settings on the subsequent import raw data form.

Click import. If you hear nothing but pure white noise, the audio is probably encrypted. Unless you have access to the SIP traffic, you may be out of luck. If you heard what sounds like spoken words, but it sounds too fast or poor quality, you may need to try different variations of encoding, channels, and sample rates.

Step 5 - Panic


If it works, you can export it from audacity as a .wav file as evidence. Let your client or boss know the bad news. This isn't a well documented vulnerability, but from what I can tell you can at least solve the privacy concerns by encrypting the RTP traffic. You'll also want to ensure SIP is encrypted as well, as encryption keys are sent using the signalling channel.


TODO


I've started work on a tool that'll remove the need to run rdpnatscan as a separate tool, and make it more suitable for pentesters, but it needs a lot more work and testing.


2024-04-12 Update, we have released to tool to exploit this vulnerability without going through quite so many steps. This tool can be found on github, https://github.com/CR-DMcDonald/voipire/ .

356 views0 comments

댓글


bottom of page