|Boeing image. Boeing 747-8 Intercontinental.|
At a time when every stakeholder, governments to airlines and airports on to tax-payers and everyone in-between is spending obscene amounts of money, loss of privacy, and other resources to make the skies safer, this story is downright scary.
The worst part of this story is that this vulnerability exists due to a lack of timely updating of operating system patches. May be the Australian Transport Safety Bureau (ATSB) should be black-listing this airline.
A while back now, but many of the same systems are in place in the same way, I was contracted to test the systems on a Boeing 747. They had added a new video system that ran over IP. They segregated this from the control systems using layer 2 – VLANs. We managed to break the VLANs and access other systems and with source routing could access the Engine management systems.
The response, “the engine management system is out of scope.”
For those who do not know, 747’s are big flying Unix hosts. At the time, the engine management system on this particular airline was Solaris based. The patching was well behind and they used telnet as SSH broke the menus and the budget did not extend to fixing this. The engineers could actually access the engine management system of a 747 in route. If issues are noted, they can re-tune the engine in air.
The issue here is that all that separated the engine control systems and the open network was NAT based filters. There were (and as far as I know this is true today), no extrusion controls. They filter incoming traffic, but all outgoing traffic is allowed. For those who engage in Pen Testing and know what a shoveled shell is… I need not say more.
All I can say is YIKES!!!!! May be Unix gurus can elaborate a little more on this story.