backtop


Print 116 comment(s) - last by jimhsu.. on Dec 22 at 10:16 PM

Officials say there is no evidence that flight control systems were compromised

The U.S. military makes heavy use of UAVs in many areas of the world for reconnaissance duties. The UAV is widely used in Iraq and Afghanistan as well as in Somalia and other locations. The drones are used to track and sometimes attack targets when needed.

The Wall Street Journal reports that enemy insurgents have been able to use a commonly available piece of software to intercept the unencrypted feeds that the drone uses between the aircraft and ground control. The software used by the insurgents to capture the video feeds was a $26 app available online called Sky Grabber.

One of the developers of the Sky Grabber software told the WSJ in an email, "It [Sky Grabber] was developed to intercept music, photos, video, programs and other content that other users download from the internet -- no military data or other commercial data, only free legal content."

The military claims that there is no indication that he insurgents were able to take control of the drones or interfere with their flight in any way. However, some fear that the ability to capture the live video feeds will allow the insurgents to track the position of the drones to better avoid attack and surveillance. The big fear is that intercepted feeds could be used to discover allied troop surprise attacks and lead to the death of allied soldiers.

The interception of the video feeds from the aircraft was apparently not a onetime occurrence. In the summer of 2009, the WSJ reports that the military found "days and days and hours and hours of proof" that the video feeds were being intercepted on a laptop that was recovered from a Shiite militant.

A defense official James Clapper was asked to assess the interception of the feeds and concluded, "There did appear to be vulnerability. There's been no harm done to troops or missions compromised as a result of it, but there's an issue that we can take care of and we're doing so."

The military is working on encrypting all feeds from its drone aircraft, but adding encryption to the feeds requires not only updates be added to the drones, but updates to the control systems on the ground as well. The U.S. first learned of the flaw in unencrypted drone feeds in Bosnia during the 1990s, but the Pentagon assumed that the insurgents wouldn't know how to exploit the vulnerability.

While the evidence of feeds found was most prolific in Iraq, there is evidence that the feeds have been intercepted in Afghanistan as well. "There was evidence this was not a one-time deal," said a person close to the matter.

Fixing the security gap in the drones during the program development would have added delays according to former security officials and would have added to the cost of the drones. Even the new generation of drones called Reaper have feeds that are unencrypted.

It's unclear whether the successor to the Reaper called the Avenger will suffer from the same issue with unencrypted security feeds.



Comments     Threshold


This article is over a month old, voting and posting comments is disabled

RE: **Shakes head**
By karielash on 12/17/2009 10:55:30 PM , Rating: 3
You can update encryption algorithms and redesign or implement new hardware. Simple fact is there was hardware encryption available at the time (no matter how limited that might have been after 20 years) but someone took a conscious decision not to implement even basic levels of protection. It need not have been complex, even a delay of a few minutes between a live and a hacked video stream could make the difference between success and failure. This was a poor decision no matter how you look at it. And not correcting that mistake once it was apparent was an exceptionally bad move.


RE: **Shakes head**
By weskurtz0081 on 12/17/2009 11:51:03 PM , Rating: 2
The point is, there is probably more to it than you and I are aware of.

I agree that it was probably a mistake, but remember, hind sight is 20/20. It's easy to say they screwed up, but a little more difficult to understand what the entire scope of the decision required.

As far as redesigning hardware, often times it's not a simple task in aviation. Most of the computers on military air craft are running old hardware by consumer standards. Much of that stuff is VERY proprietary and might be rather expensive to fix/replace.

Also, remember, these drones were originally scheduled to be replaced earlier this decade, but the funding go cut.

Anyway, I don't disagree it was a mistake, and I have said as much multiple times, I just think the situation may have been a little more involved that just saying "they should have encrypted the video feed".


RE: **Shakes head**
By weskurtz0081 on 12/17/2009 11:59:56 PM , Rating: 2
One other thing to think about. Encryption still has CPU overhead, and who knows what type of encryption was available then, what kind of power it took, what type of hardware is on the drone....

Point is, there are MANY MANY different possibilities that should be considered, it was 20 years ago.

Sitting here today, I agree, it is clear it should have been encrypted, but if I were back in 1990 working for the contractor that designed it, I might not be saying the same thing.


RE: **Shakes head**
By SlyNine on 12/18/2009 3:26:34 AM , Rating: 3
They had DES in 1977, Otho it is insecure today any encryption is better then none. This combined with none standard container files and codecs could have made it very hard to intercept and make useful in a reasonable amount of time.

Remember it probably doesn't matter if they break it a month from now.

The biggest problem would be any false sense of security.


"This is about the Internet.  Everything on the Internet is encrypted. This is not a BlackBerry-only issue. If they can't deal with the Internet, they should shut it off." -- RIM co-CEO Michael Lazaridis

Related Articles
Air Force Debuts New Jet-powered UAV
April 29, 2009, 12:00 PM













botimage
Copyright 2014 DailyTech LLC. - RSS Feed | Advertise | About Us | Ethics | FAQ | Terms, Conditions & Privacy Information | Kristopher Kubicki