Oh no, you're thinking, yet another cookie pop-up. Well, sorry, it's the law. We measure how many people read us, and ensure you see relevant ads, by storing cookies on your device. If you're cool with that, hit “Accept all Cookies”. For more info and to customize your settings, hit “Customize Settings”.

Review and manage your consent

Here's an overview of our use of cookies, similar technologies and how to manage them. You can also change your choices at any time, by hitting the “Your Consent Options” link on the site's footer.

Manage Cookie Preferences
  • These cookies are strictly necessary so that you can navigate the site as normal and use all features. Without these cookies we cannot provide you with the service that you expect.

  • These cookies are used to make advertising messages more relevant to you. They perform functions like preventing the same ad from continuously reappearing, ensuring that ads are properly displayed for advertisers, and in some cases selecting advertisements that are based on your interests.

  • These cookies collect information in aggregate form to help us understand how our websites are being used. They allow us to count visits and traffic sources so that we can measure and improve the performance of our sites. If people say no to these cookies, we do not know how many people have visited and we cannot monitor performance.

See also our Cookie policy and Privacy policy.

This article is more than 1 year old

Check out this link! It's not like it'll crash your iPhone or anything (Hint: Of course it will)

A few lines of code that Apple's browser simply can't handle

Apple iPhones, iPads, and Mac computers that stray onto websites with malicious CSS code, while using Safari, can crash or fall over – due to a flaw in the web browser.

The WebKit rendering engine vulnerability can be triggered by just a few lines of code in a cascading style sheet (CSS). On iOS devices, at least, it all starts to go wrong when the browser tries to parse a processor-intensive CSS feature called backdrop-filter on nested page elements.

The so-called Safari Reaper attack – developed by Berlin-based security researcher Sabri Haddouche and uploaded to GitHub this week – effectively crashes iOS devices, from iPads to iPhones running iOS 7 to 12, and even Apple smartwatches. The CSS causes the rendering engine to exhaust the system's resources, and force the gadgets to reboot to recover.

Macs can be similarly frozen by the same exploit, forcing them to restart, so don't try this at home. Other browsers that make use of WebKit are likely also vulnerable. On systems that don't crash, the HTML renders a picture of a "triggered" Thomas the Tank Engine.

Haddouche, who works for secure messaging outfit Wire, told El Reg that the same trick crashes tabs on IE and Edge. The researcher came across the vulnerability while researching browser-crashing attacks more generally last week.

He suggested restricting nested elements and expensive CSS calls to defend against the attack.

The method is reminiscent of the "evil text" iPhone bug of 2015 except in this case we're talking about CSS. Neither vulnerability can push malware onto crashed devices so it's more a nuisance than anything else, at least by itself – it's a way to crash your pal's iThing or Mac by tricking them into opening a dodgy page in Safari. ®

 

Similar topics

TIP US OFF

Send us news


Other stories you might like