Attacks/Breaches
7/15/2013
11:01 AM
Gunter Ollmann
Gunter Ollmann
Commentary
Connect Directly
RSS
E-Mail
50%
50%

Hacking The Emergency Alerting System

More EAS devices vulnerable now than when vendors were alerted in January

Every month or so in the U.S. you'll likely hear the "BARRP BARRP BARRP ... This is a Test Message" over the radio as the station you're listening to conducts its mandatory testing of the Emergency Alerting System (EAS). This is the same system you'll have also seen in many alien invasion and impending apocalypse movies where the president of the United States interrupts all TV broadcasts with an important message.

It's also the same system that was briefly hacked in Montana, Michigan, and New Mexico in February to warn local residents of zombie attacks.

That particular hack occurred a month after the vendor for the system had been alerted to a bunch of critical vulnerabilities uncovered by Mike Davis of IOActive Inc., and several months prior to the firmware updates being available for owners of the system to apply.

As it happens, the vulnerability exploited in the February "zombie attack" alerts appears to have been as trivial as knowledge of default shipping passwords that hadn't been changed by the TV stations.

Last week CERT and IOActive (PDF) released advisories detailing the nature of the vulnerabilities and provided links to the updated firmware patches by the vulnerable vendors -- Digital Alert Systems and Monroe Electronics.

There was some confusion at the time because the vulnerable vendors appeared to have released patches for some of the undisclosed vulnerabilities earlier; their press release of June 13 is dated April 24th (the date of when the vendors supposedly began outreach to their vulnerable customers).

Regardless, the most critical vulnerabilities -- the compromised SSH root key, default passwords, and predictable password generation -- allow attackers to trivially take control of the vulnerable systems and override station broadcasts.

The EAS itself is categorized as critical national infrastructure, yet it appears to still be largely vulnerable to attack even months after various security updates and alerts have been released. In a blog late last week, the original discoverer of the vulnerabilities, IOActive's Davis, indicated that more of the system is vulnerable to attack than it was when he'd alerted the vendors back in January.

I've heard a few ill-informed rumblings that even if the EAS were hacked again, it would just be a nuisance. In the most trivial case, if the system were to be hacked again and the hackers were to issue repeated "zombie apocalypse" warnings, people would likely lose confidence and trust in the system -- meaning that in the time of a real emergency, people may not follow the real advice, and lives could be lost.

Alternatively, if I were employed by a foreign military organization, hacking the EAS would be fairly high up on my list of critical infrastructure assets to target. Not only could I usurp control of the system to release disinformation and sow confusion, I could probably do so without falling afoul of too many articles of war. In addition, with access to the system I could also deny broadcasts by the legitimate broadcasters -- either by continually broadcasting my own messages or by replacing SSH keys and changing passwords to prevent their future access.

To prevent these scenarios from coming into play, it is critically important that the various broadcasters and their system administrators secure the Digital Alert Systems and Monroe Electronics EAS devices --- by applying the latest security updates, changing default passwords, and doing their best to restrict Internet access to the devices from unauthorized IP addresses. At the present time, there are lots of vulnerable devices and knowledge of the vulnerabilities is now public.

BARRP BARRP BARRP ... This is Not a Test!

Gunter Ollmann, CTO, IOActive Inc. Gunter Ollmann serves as CTO for IOActive Inc. where he is responsible for the strategic vision of the security services portfolio, driving new research areas and bringing new services to market. With over two decades in the information security arena, Gunter has stared down ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Becca Lipman
50%
50%
Becca Lipman,
User Rank: Apprentice
7/16/2013 | 10:35:58 PM
re: Hacking The Emergency Alerting System
Some things just fall under the security update radar, making them easy targets for hackers looking to test their budding skills. I can't help but think this is one of those examples. To me, Zombie attack alerts reek of high school kids who have suddenly stumbled upon some sweet hacking codes. But as you say, this could easily do some serious damage and lessen confidence in the warning system. Warning! Warning!
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2009-5142
Published: 2014-08-21
Cross-site scripting (XSS) vulnerability in timthumb.php in TimThumb 1.09 and earlier, as used in Mimbo Pro 2.3.1 and other products, allows remote attackers to inject arbitrary web script or HTML via the src parameter.

CVE-2010-5302
Published: 2014-08-21
Cross-site scripting (XSS) vulnerability in timthumb.php in TimThumb before 1.15 as of 20100908 (r88), as used in multiple products, allows remote attackers to inject arbitrary web script or HTML via the QUERY_STRING.

CVE-2010-5303
Published: 2014-08-21
Cross-site scripting (XSS) vulnerability in the displayError function in timthumb.php in TimThumb before 1.15 (r85), as used in multiple products, allows remote attackers to inject arbitrary web script or HTML via unspecified vectors related to $errorString.

CVE-2014-0965
Published: 2014-08-21
IBM WebSphere Application Server (WAS) 7.0.x before 7.0.0.33, 8.0.x before 8.0.0.9, and 8.5.x before 8.5.5.3 allows remote attackers to obtain sensitive information via a crafted SOAP response.

CVE-2014-3022
Published: 2014-08-21
IBM WebSphere Application Server (WAS) 7.0.x before 7.0.0.33, 8.0.x before 8.0.0.9, and 8.5.x before 8.5.5.3 allows remote attackers to obtain sensitive information via a crafted URL that triggers an error condition.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Three interviews on critical embedded systems and security, recorded at Black Hat 2014 in Las Vegas.