News for hackers. Stuff that matters.
Re:BMW are complying with the GPL by suzeanne on Tuesday March 29, 2016 @07:14PM (#11385734)
Interesting: BMW did share the OSS they used, and in the process they also revealed lots of outdated packages in use. This of course leads me to wonder: Vulnerabilities?

It is after all an Internet-connected vehicle.

Despite the article author's recognition given for BMW's OSS compliance, I am dismayed to see yet another example of likely inconsideration given toward implementation of security in the engineering of an Internet-connected vehicle.

This sort of negligence is eventually going to result in some rather ugly outcome.

Re:BMW are complying with the GPL by Sanddancer on Tuesday March 29, 2016 @08:39PM (#11386154)
From the looks of it, they used the OSes the chipmakers provide in their reference packages. The stlinux stuff seems ripped pretty much verbatim from stlinux 2.4 [0] and the rest seems to be from Freescale/NXP's reference linux for their i.MX series [1]. Automakers, like a lot of other entities, rarely make their own distros themselves, but rather tend to use the reference OS provided by the chipmakers.

[0] ftp://ftp.stlinux.com/pub/stlinux/2.4/

[1] http://www.nxp.com/products/microcontrollers-and-processors/...

Re:BMW are complying with the GPL by cmurf on Tuesday March 29, 2016 @11:46PM (#11386832)
With software this old, there certainly are vulnerabilities, probably full on exploits available, that have also long since been patched. The attack surface of new products using old software is much higher than it ought to be. And consider not is it in need of updating before it's being driven off the lot, it's likely to have service updates for a time frame shorter than its useful service life.

We're doing this wrong.

Re:BMW are complying with the GPL by xyzzy_plugh on Wednesday March 30, 2016 @02:51AM (#11387411)
You'd be surprised at the amount of effort to apply upstream patches or fixes to older vendor software. Many vendors also maintain older forks indefinitely. I've spent an inhumane amount of time applying/porting modern security fixes to ancient codebases.

The root of the problem is: you buy a part, and to use the part you need some software to talk to it. The vendor, along with the part, supplies you with some sample code, which uses some ancient kernel and ancient GPLv2 utilities. If you use their code, then you perpetuate the problem. If you choose not to, then they won't help you when you have issues.

Why do vendors use such ancient software? Vendors care deeply about their IP, and to some extent tivoization does happen with individual products, but more usually through obfuscation. Not a whole lot of open firmware for wireless chipsets, is there?

Customer demand can change things, but vendors are afraid of their customers stealing their technology, and taking it to a cheaper competitor, or building it themselves. This stuff happens all the time. So they give you some code that talks some foreign language to their part or give it a seemingly black box blob of code to run and suddenly it's a black box to you too.

Patents (for hardware), and China's lack of concern for IP theft are the root of all of this.

Re:BMW are complying with the GPL by adrianratnapala on Wednesday March 30, 2016 @04:08AM (#11387670)
I think there is something more primal going on too.

Vendors might at some time chose to say "freeze" and now we will just deliver this same binary blob, or at best generate new binary blobs from an ancient source stack we have under version control.

Making changes means, at best, going through an expensive testing procedure. At worst, there is no such procedure and all change is an anethema.

So they only make changes when they have to, and as the cost of staying obsolete increases, so does the cost of becoming up to date.

Re:BMW are complying with the GPL by xyzzy_plugh on Wednesday March 30, 2016 @04:21AM (#11387736)
I tend to agree, but remember that for many vendors providing code that doesn't run/isn't tested on some LTS kernel means no one will use it. Or, you'll incorporate the vendor delivering support as part of the deal.

Many times I've spent late nights babysitting an employee from $VENDOR debugging/fixing/rewriting their driver to play nice with our stack.

Re:BMW are complying with the GPL by coldpie on Wednesday March 30, 2016 @08:16AM (#11388681)
This is why you never connect anything that isn't running a supported and update-able operating system to the internet. That includes your car, your TV, your washing machine, your printer, your fridge, and your old Windows XP box.
Re:BMW are complying with the GPL by belorn on Wednesday March 30, 2016 @03:46AM (#11387580)
I would guess that they have a package filter to prevent those vulnerabilities to be exploited. It seems a rather standard practice in places where updating is not a easy option, either because it breaks things or because of bureaucratic verification process, but where filter rules can easily be kept updated.
Re:BMW are complying with the GPL by suzeanne on Tuesday March 29, 2016 @09:05PM (#11386260)
Excellent reply.

Indeed, quite true.

Though none of this excuses any negligence, no matter if it is the vendor of the manufacturer.

Re:BMW are complying with the GPL by deathanatos on Wednesday March 30, 2016 @12:51AM (#11387043)
> Despite the article author's recognition given for BMW's OSS compliance, I am dismayed to see yet another example of likely inconsideration given toward implementation of security in the engineering of an Internet-connected vehicle.

I hear you, but isn't this one of the reasons for wanting compliance around the (L)GPL? It allows us, the owners of the vehicle and users of the software to make that inspection, and hopefully, patch the vulnerabilities in the software, right? (I believe one of the provisions of the LGPL is that it must be possible to replace the LGPL'd software with a different version — this is why most software dynamically links to LGPL libraries: it allows the .so/.dll to be "simply" swapped out for a different one.)

Re:BMW are complying with the GPL by bonzini on Wednesday March 30, 2016 @05:37AM (#11388076)
Unless you're using v3 of the LGPL, the provision only extends towards providing separate object files for the program (if statically linked) or separate shared library files for the library (if dynamically linked). It is pretty much useless if you have no means to install a modified binary.
Re:BMW are complying with the GPL by a3n on Tuesday March 29, 2016 @07:37PM (#11385860)
Total guess: as a regulated company, they may have to get approval for their code, which would include validated versions of 3rd party code. If they have to go through that with any new version of 3rd party code, they may not want to make that effort.
Re:BMW are complying with the GPL by suzeanne on Tuesday March 29, 2016 @08:01PM (#11385960)
Well, the first time a hacker vehicle exploit results in one or more deaths of the driver and/or passengers of one of these Internet-connected vehicles, it's going to be all over the news. Right around then... and when the lawsuits hit, some execs/directors are going to realize that such effort is far less costly than the PR disasters that can unfold when corners are cut.

I mean, obviously some people at Volvo thought that actual emissions compliance was far too costly to bother with --and that didn't even result in a vehicle accident or personal injury. Certainly their bottom line has had a major impact as a result. The potential for PR disaster with Internet-connected vehicles is certainly much more concerning.

The inevitability of some such future tragedy and resulting media-fueled PR disaster for one or more vehicle manufactures is a certainty. It's only a matter of when and which vehicle manufacturer(s) will be liable. When that happens, I’m certain that such sizable companies can figure out how to streamline the approval process with whatever regulatory bodies might be involved, or they’ll just learn to live with the pain… for being for less than the much greater pain of a PR disaster.

Re:BMW are complying with the GPL by slgeorge on Tuesday March 29, 2016 @08:12PM (#11386013)
> Well, the first time a hacker vehicle exploit results in one or more deaths of the driver and/or passengers of one of these Internet-connected vehicles

It's the infotainment system according to one of the original blog posts. And in fairness the previous post was all about the updates they were providing - albeit unencrypted.

Re:BMW are complying with the GPL by suzeanne on Tuesday March 29, 2016 @08:55PM (#11386219)
It doesn't matter if it's the infotainment system so long as it's connected to the rest of the electronics. Yes, hacks have already exploited critical vehicle controls via Internet infotainment systems. So long as vehicle manufacturers do not physically separate the electronics, such vulnerabilities will surface. Currently, the standard practice is to build out the electronics for a vehicle as a single system.
Re:BMW are complying with the GPL by kaftoy on Wednesday March 30, 2016 @09:12AM (#11388961)
> Currently, the standard practice is to build out the electronics for a vehicle as a single system.

What do you mean by this? The car itself is a single unit so you can assume the electronics inside communicate at some level (CAN networks usually), but the electronics are separated. You have a control unit for the engine, another one for the ABS, another for the gearbox and many others for various body control functions. Some of them communicate with each other over the CAN, but only transmit/receive messages of particular interest. For example, the ABS unit in some cases tells the engine control unit the vehicle speed. The engine control unit transmits the engine RPM to the body control unit for obvious reasons. The same for the anti-theft mechanism.

To the subject: Having outdated drivers in production level software is common practice. During final validation of the SW, before start of production, if some drivers are found outdated (even declared invalid by the driver/package owner), people do not jump to upgrade immediately. It undergoes a process of analysis: is there any critical bug which the new version fixes? Does it impact the current project configuration? If not, why upgrade? You run the risk of introducing a regression => requires extra validations which can take weeks or months. Nobody will approve that just to fix some bug without functional impact in that particular system. So when you claim that a certain package has to be updated to the latest version, you have to come up with arguments. "Newest is always better" does not count. There are countless examples when newer versions of some piece of SW fixed some bug but broke something that was working. SW updates after the majority of the validation process is finished happens only on a NEED TO HAVE basis.

Re:BMW are complying with the GPL by noselasd on Wednesday March 30, 2016 @02:01AM (#11387253)
I'd rather wait until your claims of security issues and remote hacks are verified for the particular vehicle here.

All of this is just crying wolf so far.

Re:BMW are complying with the GPL by nitrogen on Wednesday March 30, 2016 @05:13AM (#11387969)
Remote-drive vulnerabilities have been demonstrated in infotainment systems, proving that the class of vulnerabilities is real. There's no need to prove it can happen for every single vehicle to be concerned about general best practices.
Re:BMW are complying with the GPL by noselasd on Wednesday March 30, 2016 @04:26PM (#11392698)
Yes there is. If this system have no write ability onto the relevant CAN-bus, the class of vulnerability you talk about (which comes from the Jeep hack) does not exist.

But sure - best practices should be followed.

Re:BMW are complying with the GPL by bigiain on Tuesday March 29, 2016 @08:45PM (#11386181)
Wasn't the Wired article reported Jeep hack done via the infotainment system (through an improperly implemented one-way connection to the canbus, from memory)?
Re:BMW are complying with the GPL by suzeanne on Tuesday March 29, 2016 @08:57PM (#11386228)
Yes, precisely: "Miller and Valasek’s exploit uses a burner phone’s cellular connection to attack the Jeep’s internet-connected entertainment system." http://www.wired.com/2015/07/hackers-remotely-kill-jeep-high...
Re:BMW are complying with the GPL by a3n on Tuesday March 29, 2016 @11:58PM (#11386868)
And the CIO at Target probably said "It's only the HVAC system." :)
Re:BMW are complying with the GPL by catnaroek on Tuesday March 29, 2016 @08:06PM (#11385984)
You're confusing Volvo with Volkswagen.
Re:BMW are complying with the GPL by Swizec on Tuesday March 29, 2016 @08:47PM (#11386187)
Which just goes to show the real impact of that PR disaster -> none. People can't even remember correctly which of the 3 or 4 largest car brands in the world it was.
Re:BMW are complying with the GPL by PhasmaFelis on Wednesday March 30, 2016 @12:14AM (#11386925)
Their stock price dropped by like 40% in a few days. I think that trumps "one person on the internet got a name confused."
Re:BMW are complying with the GPL by Nutmog on Wednesday March 30, 2016 @03:46AM (#11387577)
That's not obvious at all. Their share price has now recovered half way to where it was, so you should call that a 20% drop when comparing to what people remember today (not the few days after news broke). Not only that, it was already in an even bigger decline during the year leading up to the emissions scandal, and that decline instantly stopped. Compared to the pre-scandal trend, you could almost argue that their share price has improved since the scandal.

Look at the graph. http://finance.yahoo.com/echarts?s=VOW.DE+Interactive#{"allo...

Re:BMW are complying with the GPL by BBlarat on Wednesday March 30, 2016 @03:46AM (#11387576)
I'm not following Volkswagon stocks, but did they bounce back up after a while or are they stuck in a down? If they're still down than yes that trumps, but if it got back up after a while I guess some people made loads of money on this debacle but VW seems unharmed.
Re:BMW are complying with the GPL by dagw on Wednesday March 30, 2016 @04:13AM (#11387702)
They bounced back a bit, but they're still more than 20% off what they where the day before the scandal broke and att almost half of their 12 month peak.
Re:BMW are complying with the GPL by Too on Wednesday March 30, 2016 @12:24AM (#11386958)
Re:BMW are complying with the GPL by suzeanne on Tuesday March 29, 2016 @08:52PM (#11386202)
True, I typo'd. Thank you for correcting me.
Re:BMW are complying with the GPL by skoczymroczny on Wednesday March 30, 2016 @06:52AM (#11388331)
Or they will phrase it as "Hacker uses open sourced BMW code to find a vulnerability resulting in a fatal vehicle crash", "If they hadn't opensourced it, it wouldn't have happened!"
Re:BMW are complying with the GPL by ChristianBundy on Tuesday March 29, 2016 @08:58PM (#11386233)
> Well, the first time a hacker vehicle exploit results in one or more deaths of the driver and/or passengers of one of these Internet-connected vehicles, it's going to be all over the news.

Michael Hastings, anyone?

Re:BMW are complying with the GPL by Animats on Tuesday March 29, 2016 @10:40PM (#11386605)
Not Volvo - Volkswagen.
Re:BMW are complying with the GPL by suzeanne on Tuesday March 29, 2016 @11:46PM (#11386835)
Correct. I typoed.
Re:BMW are complying with the GPL by rconti on Wednesday March 30, 2016 @12:31AM (#11386984)
I suspect the first time that happens, automakers will move away from FOSS so that the can at least hide what outdated junk they're using.
Re:BMW are complying with the GPL by adrianN on Wednesday March 30, 2016 @01:34AM (#11387167)
Exactly this. All software in safety critical components needs to be validated. Validation is very expensive, especially if you can't argue that it's "industry standard" software, so an already validated piece of software nearly always wins over alternatives.
Re:BMW are complying with the GPL by hkmurakami on Tuesday March 29, 2016 @10:15PM (#11386513)
On the hardware side, the product development cycle for a car is about 5 years, which design lockins in stages along the way (there's a mad rush for a "land grab" for engine compartment space by suppliers many years in advance to the actual launch of the car).

It wouldn't surprise me if the software had a similarly long development and lock-in cycle.

Re:BMW are complying with the GPL by intrasight on Wednesday March 30, 2016 @01:08AM (#11387096)
Open-source vulnerabilities are much less scary than closed-source vulnerabilities.
Re:BMW are complying with the GPL by datashaman on Wednesday March 30, 2016 @05:42AM (#11388098)
only if the code is updated.