smartnuts … the world on the cabaret-style dissecting table

Glitch as you can as soon as you can

G

The digital world’s a bit of a wild west, mate. And we’re not just talkin’ dodgy online banking, half-baked crypto wallets, or sensitive corporate data sitting in cloud servers just waitin’ for some muppet to poke holes in a provider’s rusty infrastructure. Nah – even just takin’ a modern car for a spin can turn into one hell of a ride if someone else decides to take the wheel – digitally, that is.

Back in the day, car hacking was more of a niche sport – few remote-exploitable bugs, not really scalable, needed specialist skills, and even when they cracked it, hackers couldn’t do much more than fiddle around the edges. A bit of a hacker’s hobby, really – maybe a few rogue tuners trying their luck. Carmakers (OEMs) got wise eventually – some ‘cause they wanted to, others ‘cause regulations like UN R155 or China’s GB 44495-2024 gave ‘em a solid nudge. They started beefin’ up the electronics with better protection. But here’s the kicker: the defences going into today’s cars were dreamed up 6 or 7 years ago. Yep – ages before the thing ever rolled off the production line. And while the hackers keep levelling up thanks to tech progress, those older defences have to hold their ground for the whole lifecycle of the vehicle’s electronic brain.

Now, if you’ve planned your security right – thinkin’ state-of-the-art, security-by-design, and keeping it tight over the full life of the car – then you’re mostly sweet. Sure, you might still cop the occasional curveball – say, if quantum cryptography finally gets its big break – but that’s rare as a white roo. Still, it’s enough to make top execs sweat when they imagine profits evaporating thanks to a cyber break-in.

All this assumes the environment’s playin’ nice – that OEMs see cybersecurity as a chance to stand out from the mob, cut costs by fixin’ stuff early, and stay on the right side of regs. But let’s be honest – with global uncertainty and the bean counters breathing down everyone’s neck, things can get a bit dicey. In times like these, carmakers might be tempted to stick with the old toolbox instead of pushing for new ground. Problem is, by focusing on short-term gains, they risk missin’ future threats. Skippin’ the upfront work means higher costs down the track. “No worries,” they think, “we’ll just push a software update later.” But that only works if you don’t need to rip out and replace actual hardware. If you do? Well, say goodbye to your rosy profitability forecasts, mate.

And here’s where things get spicy: regulators and the tech services carrying out their rules aren’t muckin’ around anymore. Take China’s GB 44495-2024 – it’s got a whole list of ultra-specific test cases that OEMs have to nail before their cars can hit Chinese roads. That’s not just a speed bump – it’s a full-on gatekeeper move. But maybe it’s also smart. They’re thinking ahead, getting ready for tomorrow’s threats. Case in point: glitching attacks. Not exactly in every hacker’s toolkit yet, but they’re comin’. These voltage glitching moves mess with a device’s power supply – give it a quick zap, and boom, you might get it to skip checks, run dodgy code, or just trip up entirely. Nasty stuff for embedded systems like ECUs in modern cars. Used to be, stuff like probing a PCB with pin tools sounded like science fair nonsense – more of a “can we?” than “should we?”. But now, with GB 44495-2024 laying down the law and tech services turning theory into practice, things are changing fast. Suddenly, OEMs aren’t just tossing over cars or parts for inspection – they’re handing over actual circuit boards so someone with a multimeter can have a go. Right now, they’re mostly trying to tease out responses from the hardware, not rewrite the silicon-level logic. But give it time. Especially with cars moving into higher levels of automation, you can bet glitching will be on more regulators’ radar sooner than later.

Bottom line? If you’re an OEM, and you’re still sleeping on this – it’s time for a wake-up call. You’ve gotta future-proof your systems now, not once you’re already copping flak in the field.

Link to the German version of this article

About the author

Michael Bunzel

Michael Bunzel (aka maschasan) is a lawyer and engineer currently living in Germany. He has been working in the field of Cybersecurity and related laws and regulations for over 25 years now.

Mike took on various roles and functions in the context of Information Security, Cybersecurity, and SCADA/Shopfloor Security at a German car manufacturer in southern Germany for more than fifteen years - currently in the R&D resort, with focus on E/E-systems in the context of automotive cybersecurity and related regulations in different markets (e.g. UN, EU, China, Korea, India, US, and others).

Mike has worked with global organizations across dozens of countries, cultures and languages, well-travelled in EMEIA, APAC and the Americas.

All articles in this blog do NOT reflect the opinion of his employer, but are all an expression of his personal view of things.

By Michael Bunzel
smartnuts … the world on the cabaret-style dissecting table

Get in touch

Tags