Apple: The flaw that caused iPhones to crash is still not fixed despite many updates

Despite multiple updates to iOS 17 since the first report in September, Apple still hasn’t fixed a critical vulnerability exploited by the Flipper Zero device that was causing iPhones and iPads to crash. The attack, which used a faulty Bluetooth pairing sequence, remained unsolved. This raises concerns about Apple’s effectiveness in fixing such problems.

As a reminder, hackers took over Flipper Zero, a portable device for network frequency testers. Second, it had been turned into a tool capable of performing denial-of-service (DoS) attacks. Flipper Zero exploits a flaw in Bluetooth Low Energy (BLE) pairing to flood iPhones and iPads with fake Bluetooth connection pop-ups. causing devices to crash and eventually reboot.

Also read – Why the flaw that crashes iPhones is nothing to worry about for Android users

It takes time for Apple to fix the problem with its iPhones

The vulnerability lies in the BLE technology that Apple uses in various ecosystem functions such as AirDrop, HandOff, iBeacon, HomeKit, and Apple Watch features. Specifically, the attack exploits the ability to spoof advertising packets (ADV packets) used to identify local devices. This flaw allows hackers to flood Apple devices with fake notifications by taking advantage of the seamless pairing experience that BLE provides For operations like connecting AirPods.

The Flipper Zero attack, where the Bluetooth radio range is approximately 50 meters, requires the attacker to be nearby. However, what creates problems is the lack of a defense mechanism. Right now, The only recommended precaution is to disable Bluetooth in the device settingsa solution that significantly limits functionality and is temporary due to Apple restoring Bluetooth functionality after system updates.

Despite various reports from users stating that they have fallen victim to this flaw, Apple has been slow to fix the problem. Some believe this, although technical difficulties may contributeApple may not consider this flaw a big enough threat prioritizing quick resolution; because this does not compromise your user data, for example.