February 28, 2010
Posted by on
I have written a letter to the people in charge of the SIP scanning and owner of the network. I have now sent it to several IP responsible for those IP addresses.
Dear support personnel
We have repeatedly been scanned for open SIP (VoIP) access from IP
adresses: 220.127.116.11, 18.104.22.168 and 22.214.171.124.
The last time was February 27th 2010, but this scanning has been going
on for a long time, first reported back in December 2009.
We believe this is fraudulent activity to scan for open SIP gateways to
route traffic towards the telephony network.
Please inform the owners of these servers that this activity is not
tolerated and seen as an attack on our servers.
February 22, 2010
Posted by on
A Chinese based server has been very active latest days, and googling the IP addresses ( 126.96.36.199 and 188.8.131.52 ) tells me they have been scanning a long time.
One guy with an Asterisk got hit December 2009 and others back in November. Others starts debugging and asks what it is in public support forums. There will be even more of this scanning coming next months!
Some has added firewall rules like:
But this will not last long until some new IP addresses show up.
What to do about it?
Secure your IP PBX and don’t let port 5060 be open for everybody.
If you must, have very long and strong passwords on all extensions. (or use port knocking..)
Make sure that callers into your PBX is not allowed onto any Outbond context making you pay their calls…
February 20, 2010
Posted by on
Old news for us in the VoIP, but a reminder for you who think you can abuse VoIP systems and get away with it..
Dan York has a good overview of it on his blog:
Updating a story we have literally been following for years ever since it broke back in July 2006, the FBI recently issued a news release indicating that Edwin Pena pled guilty in what we have been calling the “Pena/Moore VoIP fraud case”. From the news release:
Edwin Pena, 27, a Venezuelan citizen, pleaded guilty before U.S. District Judge Susan D. Wigenton to one count of conspiracy to commit computer hacking and wire fraud and one count of wire fraud. Judge Wigenton continued Pena’s detention without bond pending his sentencing, which is scheduled for May 14.
February 4, 2010
Posted by on
RIPE said a long time ago that IPv4 is running out of addresses. Now they are also allocating the 1.x.x.x network for production traffic. But this is a bit problematic, since people have been using IP addresses like 184.108.40.206 and 220.127.116.11 as examples in scripts, tools and manuals. People who don’t know any better, they try contact these. When they routes to these networks where alive, a LOT of traffic started coming in.
What made it interesting for Sandro in EnableSecurity was that most traffic was UDP (60 %) and almost 90 % to IP addresss 18.104.22.168. This is a text from RIPEs article about it:
We found that almost 60% of the UDP packets are sent towards the IP address 22.214.171.124 on port 15206 which makes up the largest amount of packets seen by our RRC. Most of these packets start their data section with 0x80, continue with seemingly random data and are padded to 172 bytes with an (again seemingly random) 2 byte value.
This can actually be RTP traffic (VoIP audio traffic) generated from hosts that are vulnerable to SIP INVITE attacks, as Sandro points out in his comment and on his blog.
This is also alarming! This scanning with default RTP audio to IP 126.96.36.199 and port 15206 seems to be doing REALLY well on the Internet. There are a lot of VoIP unsecure platforms accepting and responding to ANY SIP INVITE they get. The software doing it is NOT SIPVicious, but another. It normally uses port 3058 to send the SIP INVITES from. If anybody knows something about this software, please contact me.
I have had a slide in my VoIP presentations about this scenario. If you do a SIP INVITE sweep, you should NOT have a valid IP address for the audio. Every successful INVITE would then generate at least 20 seconds of 0,1Mbit per second stream (g711 audio) to your IP address. Your SIP INVITE sweep with your IP as receiver for RTP traffic will not take long before it backfires on you and you get a DDoS on yourself (well earned though IMHO).
So what is next?
I would love to have a honeypot or get access to the traffic going to port 188.8.131.52. All hosts that would send RTP traffic to this address, should be contacted and asked to secure their servers!
Status now from RIPE:
Since the traffic patterns seemed to be stable we decided to withdraw the announcement of 184.108.40.206/24 and 220.127.116.11/24 on 2 February 2010.