There's a lot of posts mentioning that a scan shouldn't cause any trouble, however there's no way of knowing how the services are configured on the other end, or how they are set up to respond to certain packet types, or how the server will respond to certain data within those packets if said data does not conform to expected lengths etc. A lot of assumptions are made that non-conforming data will be ignored in a clo…
I remember about 20 years ago, you could crash any Windows computer you had the IP address of by sending a particularly crafted package to a certain port. Oh, those were the days.
Boeing 787 In Flight Entertainment System Security fun
131–140 of 147 posts
Re: Boeing 787 In Flight Entertainment System Security fun
#132Earlier quoted context omitted.
It crashed due to faulty wiring in the IFE, which started an electrical fire. It could just as easily have been the coffee maker.
Well, imagine a fire due to faulty wiring that is accidentally triggered by some hack. Maybe absurd but not impossible. Why mess with any in-flight system?
Re: Boeing 787 In Flight Entertainment System Security fun
#133Earlier quoted context omitted.
Optoisolators are a prolific and an extremely cheap electrical component that performs the "air-gap" functionality.
Electrical safety airgapping and information security airgapping are different, and entirely unrelated. If data can pass from one side to the other it's not airgapped (from an infosec perspective).
Re: Boeing 787 In Flight Entertainment System Security fun
#134Earlier quoted context omitted.
This isn't a publicly accessible system like a webserver. This is an entertainment device on a plane.
It's not your intuition about the IFE hardware that's problematic; it's your intuition about the "publicly accessible system like a webserver".
Re: Boeing 787 In Flight Entertainment System Security fun
#135Beside a scan is good or bad, how would they go about finding the source? There wont be an IT officr at landing collecting logs/mac address from any wireless card. I've scanned those systems many times and nothing ever happened - i am just pointing out to the issue that catching a real attacker it is hard not just technically but in practice
Also, don't use a typical *nix terminal that looks all hackerish (black background, green font, something like that). Someone non technical is bound to notice that, even if out of the corner of their eye.
Unfortunately nowadays "Arabic" is what worries people, even if that turns out to mathematical notation. [1]
[1] https://www.theguardian.com/us-news/2016/may/07/professor-fl...
Re: Boeing 787 In Flight Entertainment System Security fun
#136There's a lot of posts mentioning that a scan shouldn't cause any trouble, however there's no way of knowing how the services are configured on the other end, or how they are set up to respond to certain packet types, or how the server will respond to certain data within those packets if said data does not conform to expected lengths etc. A lot of assumptions are made that non-conforming data will be ignored in a clo…
Irresponsible and stupid perhaps, but a lot of exaggeration here too. I'd say the absolute worst case scenario is that the IFE crashes and must be restarted. Not a great result but not a plane crash and not a 10h flight without IFE either.
Re: Boeing 787 In Flight Entertainment System Security fun
#137I'm not too keen on the idea that I'm now supposed to watch on a laptop. If I wanted to go to that kind of trouble I wouldn't be confining myself to whatever crap was on the in-flight entertainment system in the first place.
I'm not too keen on having a screen I don't control ( and never use anyway) in front of me for an entire flight. I hate being shown ads, and the only place I still regularly encounter them are airplane IFE systems I can't turn off during certain phases of the flight, and poorly chosen gas stations. Interestingly neither of those used to be significant sources of advertising.
Re: Boeing 787 In Flight Entertainment System Security fun
#138Earlier quoted context omitted.
Irresponsible and stupid perhaps, but a lot of exaggeration here too. I'd say the absolute worst case scenario is that the IFE crashes and must be restarted. Not a great result but not a plane crash and not a 10h flight without IFE either.
I'm not sure that there's any exaggeration in my post - I didn't mention any overblown outcomes that could result from these sort of actions, purely the considerations that weren't taken into account before the action was taken. I may not be seeing the wood for the trees though - it's been one of those days at work today! :)
The other almost-catastrophic outcome is apparently that the IFE system would not just crash, but be bricked in a state where it couldn't be restarted. Not impossible, but not likely either.
People switch seats in planes without asking the staff. That's also irresponsible and dangerous, and the worst case scenario is a crash. This is about the same level of risk if you ask me.
Re: Boeing 787 In Flight Entertainment System Security fun
#139Earlier quoted context omitted.
Lots of things have faulty wiring, but they keep working as long as their power draw is under some limit. Drawing excess power is a common result of software going into an infinite loop, which is a possible outcome of security probes. Half the bugs I notice in Chrome, I notice because my laptop fan starts running.
Sure. Hair dryers draw excess power when you drop them in a bathtub. Ground-fault protection outlets are supposed to prevent that. If they don't, the outlet is faulty . The origin of Murphy's Law was in a rocket sled project. This guy was strapped onto a rocket sled, fired down a track, and then subjected to strong braking forces. "If anything can go wrong, it will go wrong" didn't just mean "stuff happens". It meant…
And read this before dropping your hair dryer in the bathtub: https://iaeimagazine.org/magazine/2010/01/16/the-illusion-of...
Re: Boeing 787 In Flight Entertainment System Security fun
#140Earlier quoted context omitted.
Is this still true with 787? [1] indicates that it uses virtual links that are not physically separated. [1] - https://en.m.wikipedia.org/wiki/ARINC_429
The protection lies between that bus and the TCP/IP stack of the IFE. Data can go one way, and several feet of certification documents are there to ensure that.