VoIP Tech Chat

Fanatical Support

Got Rackspace? Got WordPress? If so… you may just have a problem.

We’ve been getting calls today from Rackspace clients (hosting WordPress sites) that have been compromised similarly to the GoDaddy hack a few weeks back. The Unmask Parasites Blog has an excellent article on the attack posted on their, well, their blog.

There are some huge sites that have been hit, and some not-so-large as well (we personally were hit by an earlier attack). In the “Is Cloud the answer” debates, this will surely become an example of how a compromise in the cloud, can devastate an entire farm.

Update 6/19/2010

Shortly after this article was initially posted, Rackspace via their Rackcloud Twitter account posted the following message: Read the rest of this entry »

The VoIP Users Conference provides an open-to-all weekly conference call where anyone can engage in discussions related to, well, VoIP. Sometimes the conversations discuss new technologies / products. Sometimes discussions center around implementation. And lately, conversations may focus on security.

Last week, Ward Mundy, Tim Panton, Karl Fife, Leif Madsen, Yours Truly, and many other regulars discussed a SIP Caller ID Injection Hack. As in all conversations, opinions differ. My position about where to best filter this injection differed than Ward Mundy’s thoughts… and, courtesy of the VoIP Users Conference, you can listen to the conversation and form your own opinions.

Although, next time… maybe you’d enjoy actively participating in our conversations rather than listening to the replay.

→ SIP Hacks: who should filter what, where? (VoIP Users Conference)

(The VoIP Users Conference provides weekly live discussion about VoIP, SIP, Asterisk and all kinds of telephony-related topics every Friday at 12pm EST. For more information, please visit http://vuc.me.)

Whoops. My bad.

LifeLock promises to “take control” of your identity — they just don’t tell you who gets to take control. Patrick and I chatted a while back about Todd Davis, the CEO of LifeLock, and how his ads promoting the ability of his company to protect identity, actually helped with the theft of his own. Back in 2007, a gentleman in Texas had used Davis’ identity to obtain a $500.00 without Davis’ knowledge. In fact, Davis only had learned about it after the unpaid loan was sold to a debt collection agency — but that’s old news.

Today, thanks to the Phoenix News Times, we learn that Davis had his identity stolen a grand total of 13 times. Or, at least 13 times that we know of.

With attention grabbing ads that published Davis’ Social Security Number, LifeLock caught the attention of many customers; as well as the FTC — who accused the company of running a scam operation and fined them $12 million dollars.

Additional Reading

• Cracking LifeLock: Even After a $12 Million Penalty for Deceptive Advertising, the Tempe Company Can’t Be Honest About Its Identity-Theft-Protection Service (Phoenix New Times)
• Lifelock Dinged $12 Million for Deceptive Business Practices (wired.com)

Attacks from the cloud.

Just over a month ago, we reported that SIP attacks from the Amazon EC2 cloud were on the rise. While the attacks we received last month were limited to “extension only” registration attempts, one of the attacks we received this morning included what we assume was a standard dictionary attack.

The first attack came from 204.236.245.101. In less than 60 seconds, this IP attempted more than 11,500 registrations against our server. Most of these were 4 digit extensions (download the log (zipped) here). The second attack came from 184.73.4.183. In less than 90 seconds, this IP attempted more than 21,000 registrations against our server; including what we think is a standard dictionary attack complete with root, postmaster, pixadmin, etc. (download the log (zipped) here).

Read the rest of this entry »

I’ve said before that I’m a big (not a fat reference) fan of Michael Graves’ blog. Continuing his promotion of the wicked cool and useful†, Mr. Graves recently wrote about Schmooze Communications’ PBXact system.

It’s a GREAT read and I leave you with this: Magic Button. (read the article)

Related links:

• e4 Technologies
• Michael Graves on SOHO VoIP

†Yes… Wicked cool and useful. If it doesn’t meet the criteria for both, it doesn’t make his blog.

I do love their logo.

Ward Mundy, of Nerd Vittles / PBX in a Flash fame, warns of a FreePBX Security Vulnerability allowing a system to be compromised simply by displaying a CDR report in the FreePBX browser.

There is a very serious security vulnerability that needs to be patched by loading the very latest version of FreePBX Framework as soon as it becomes available for your version of FreePBX. Just displaying a CDR report in the FreePBX browser could compromise your system.

The 2.5 and 2.6 patches already have been released and probably 2.7 as well. Load this patch IMMEDIATELY!!!

Setup, Module Admin, Check for Updates on Line, Upgrade All

2.5.2.3: #4223 Security Vulnerability
2.6.0.2: #3805, #3707, #4188, #4223 Security Vulnerability

For more information, check out the PBX in a Flash Forum.

Whoops. Our Bad.

McAfee released a “faulty update” this morning causing the security program to believe a good file had gone bad. In what the company calls a “False Positive Issue,” the anti-virus software identifies a good windows file, svchost.exe, as the W32/Wecorl.a virus; causing the system to continuously reboot and lose network access.

At the University Hospital in Syracuse, NY 2,500 computers were affected; however the hospital stated that patient care was not compromised. Other public service/safety organizations were also impacted, including the Kentucky State Police, the National Science Foundation, and Illinois State University.

Read the rest of this entry »

Despite rumors, Princeton has not banned the iPad from campus. It has however, found a bug (and workaround) with Apple’s latest device.

Describing what they feel is a bug with the iPad’s operating system, Princeton recently announced (via their Knowledge Base):

Network monitoring has shown that many iPad devices have caused a problem on the campus network. These devices continue to use an IP address they have been leased well beyond the time they should. (In technical terms, the device’s DHCP client software stops renewing its lease, but the device keeps using the IP address after the DHCP lease expires. This is not a WiFi issue.) This behavior causes a disruption on the campus network.

Read the rest of this entry »

Last year, the Senate passed the Truth in Caller ID Act of 2009 (S. 30 passed unanimously) and this year, the House moved forward on their own version. Of course, moving at the speed of government, the House passed the Truth in Caller ID Act of 2010.

Truth in Caller ID Act of 2009 – Amends the Communications Act of 1934 to make it unlawful for any person in the United States, in connection with any telecommunication service or VOIP (voice over Internet protocol) service, to cause any caller identification service to transmit misleading or inaccurate caller identification information (“spoofing”) with the intent to defraud or cause harm. Prohibits construing these provisions to prevent blocking caller identification or to authorize or prohibit law enforcement or U.S. intelligence agency activities.

Read the rest of this entry »

Attacks from the cloud.

Update #1: 12 APR 2010. Amazon NOC’s response.
Update #2: 12 APR 2010. Amazon Statement.
Update #3: 13 APR 2010. Amazon Response.

Complaints of rampant SIP Brute Force Attacks coming from servers with Amazon EC2 IP Addresses cause many admins to simply drop all Amazon EC2 traffic. Generally, SIP brute force attacks attempt to register various peer names to a system and/or attempt to guess passwords of known/guesses peers or endpoints.

The complaints mentioned this weekend show an excessive amount of traffic; with some providers claiming 6GB of traffic dedicated to such attacks. Since we ourselves received an attack from an Amazon hosted server, we also reported and complained to the Amazon NOC/Abuse depts. As of this posting, no response or acknowledgement has been received from Amazon. The response from Amazon is below. Read the rest of this entry »