itguy08 wrote:
Again, they are not talking how they did it. Sure in theory all that could do it. Bu how did it happen. The fact they are not talking is interesting at the least.
If you are truly concerned, I'd contact the source. Those kind of details don't work well in news articles intended for a mass audience. The same way the technical details seldom make it in to mass media articles about Microsoft exploits. There are other avenues for that information.
There's also the point of not telling EVERYONE the method of a potentially dangerous exploit before it gets a chance to be patched.
itguy08 wrote:
Sure. But that's no different than any car on the road today. Brake lines can be loosened/cut, tires can be deflated, GPS trackers can be installed. Once anyone has physical access the game is over. It's the #1 defense in any security system. Secure physical access.
Heck, it's a long shot but I'd bet someone could take your true for a few hours each day without you even noticing it if you're like many who do not have views of the parking lot and go into work at, say 8am, lunch @12, and out at 5.
Which is why pointing out that an attack needs physical access to be viable is really pointless. Physical access is possible to almost any vehicle. Requiring a black box or OBD port access may lessen the scale of the vulnerability, but it does not lessen the danger to the individual vehicle. An exploit is an exploit and needs to be fixed.
itguy08 wrote:
You and I don't know that. I would hope that the TPMS has no capabilities to backed into the ECU. And if it does then that's a bigger issue, especially for those that use wireless sensors. Probably what they did was flood the TPMS wireless radio and used that to gain access to the ECU for reprogramming. Similarly to how they jailbreak and root iPhones and Android phones.
Seems like poor engineering if that's true, doesn't it? We know they were able to exploit those features. "How" matters from the perspective of patching it, but the end result is the same, a hacked vehicle.
itguy08 wrote:
The scary thing with the Chrysler hack is that as long as they were on the Sprint network they got VIN, IP's, and GPS coordinates for vehicles in a large geographic area. That should not be possible. That sort of stuff should be protected via SSL at the least or some sort of encryption algorithm tied to the VIN. Once I have your IP it's easy to attack it and that seems precisely what they did.
All the same information carried by OnStar, which has been hacked previously. How much are you willing to bet there isn't another lurking exploit out there in OnStar's code?
itguy08 wrote:
Yet this is the one that is getting (and I shudder at the thought) Congress to do something. So either the Onstar stuff was not that great or this is the tipping point. Take your pick.
I'll vote for tipping point. Vehicle security is going to be a huge topic over the next 5-10 years. The Chrysler attacks aren't the first, and aren't the biggest. Just the latest.
itguy08 wrote:
Nice try. Don't get me started on the security mess that is Windows and how poorly programmed that ecosystem is. Microsoft is trying but until they do a ground up re-code that ain't going to happen. That's another topic for another board. And, FYI I don't run Windows so I am concerned about security (again nice try). So rather than trying to defend poor practices, I choose to avoid them. I also don't use the excuse "they all do that".
I run Windows because I have to. So I HAVE to deal with it. We don't choose the applications, the organization's leadership does, based on organizational needs. We then choose the platform to run them. Often, that means Windows.
"They all do that" isn't the excuse. Instead, it's a demonstration that they all have problems, even when they are supposed leaders in the field. Expecting perfection from FCA when Microsoft, GM, BMW, and others have not yet achieved that is unrealistic and unfair. They ALL need to fix them. They should all be held to an equally high standard. None of them have reached that yet. Not FCA, not GM, not Toyota, not Ford.
itguy08 wrote:
GM and BMW also have poorly engineered systems. There, I said it. Doesn't change the fact that the Chrysler system seems to be the worst.
Wouldn't be an ITguy post without that final brand bash. I hope to see you chime in on future engineering and security issues with ALL brands, not just FCA.