{"id":44674,"date":"2022-01-05T15:35:00","date_gmt":"2022-01-05T15:35:00","guid":{"rendered":"http:\/\/446ea993-27e7-4a43-8698-3e54eee3dd1a"},"modified":"2022-01-05T15:35:00","modified_gmt":"2022-01-05T15:35:00","slug":"this-ios-15-bug-could-crash-your-iphone-permanently","status":"publish","type":"post","link":"https:\/\/www.threatshub.org\/blog\/this-ios-15-bug-could-crash-your-iphone-permanently\/","title":{"rendered":"This iOS 15 bug could crash your iPhone permanently"},"content":{"rendered":"
<\/div>\n

A security researcher has publicly disclosed a bug present in iOS 15.2 (and going back to iOS 14.7 and possibly earlier) relating to HomeKit that could be used to permanently crash an iPhone.<\/p>\n

Trevor Spiniolas found that by changing the name of a HomeKit device<\/a> to a large string (Spiniolas used 500,000 characters for the testing), this would crash the associated iPhone. <\/p>\n

To make matters worse, because the device name would be backed up to the user’s iCloud account, restoring an iPhone and signing back into the iCloud account linked to the HomeKit device would once again trigger the bug.<\/p>\n

According to Spiniolas, “[t]his bug poses a significant risk to the data of iOS users, but the public can protect themselves from the worst of its effects by disabling Home devices in control center in order to protect local data.”<\/p>\n

Spiniolas decided to make this bug public after initially reporting the bug to Apple on August 10, and Apple promising a fix “before 2022.” December 10, Apple then informed Spiniolas that the fix would come “early 2022,” which is when he decided to make the bug public on January 1, 2022.<\/p>\n

“The public should be aware of this vulnerability and how to prevent it from being exploited,” writes Spiniolas, “rather than being kept in the dark.”<\/p>\n

Think you might be affected by this bug? Spiniolas has outlined the process to get the iPhone working again.<\/p>\n