{"uuid": "cd92d69f-423e-47ef-8c18-548b3cb693a1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-22588", "type": "seen", "source": "https://t.me/hacking_Attack/38448", "content": "Black Hat Ethical Hacking\nApple fixes doorLock bug that can disable iPhones and iPads\n\nhttps://www.blackhatethicalhacking.com/wp-content/uploads/2021/08/Untitled-design-2-1.png Apple fixes doorLock bug that can disable iPhones and iPadsPost Views: 93 https://www.blackhatethicalhacking.com/wp-content/uploads/2021/08/BECOME-A-PATRON-AND-UNLOCK-EXCLUSIVE-VIDEOS-1.png Reading Time: 1 Minute\nApple has released security updates to address a persistent denial of service (DoS) dubbed doorLock that would altogether disable iPhones and iPads running HomeKit on iOS 14.7 and later.\nHomeKit is an Apple\u00a0protocol and framework that allow iOS and iPadOS users to discover and control\u00a0smart home appliances on their network.\n\nAs the company explained in a security advisory\u00a0issued today, the doorLock vulnerability\u00a0tracked as CVE-2022-22588\u00a0will crash affected iOS and iPadOS devices when processing maliciously crafted HomeKit accessory names.\n\nApple has addressed this severe\u00a0resource exhaustion issue in iOS 15.2.1 and iPadOS 15.2.1 by adding improved input validation which no longer allows attackers to disable vulnerable devices.\n\nDevices that received security updates today include iPhone 6s and later, iPad Pro (all models), iPad Air 2 and later, iPad 5th generation and later, iPad mini 4 and later, and iPod touch (7th generation).\n\n\u201cFour months ago I discovered and reported a serious denial of service bug in iOS that still remains in the latest release. It persists through reboots and can trigger after restores under certain conditions,\u201d\u00a0Trevor Spiniolas, the programmer and \u201cbeginning security researcher\u201d who spotted and reported the bug.\nSee Also: Complete Offensive Security and Ethical Hacking Course \u201cAll the requirements are default settings. When someone sets up their iOS device, everything is already in order for the bug to work. If they accept a malicious home invitation from there, their device stops working.\u201d\nSee Also: Microsoft: New critical Windows HTTP vulnerability is wormable Fix delayed since AugustAccording to\u00a0Spiniolas,\u00a0Apple has known about doorLock\u00a0since August 2021, 2021, but pushed the security update multiple times despite repeatedly promising\u00a0to fix it.\n\n\u201cI believe this bug is being handled inappropriately as it poses a serious risk to users and many months have passed without a comprehensive fix,\u201d\u00a0Spinolas said.\n\n\u201cThe public should be aware of this vulnerability and how to prevent it from being exploited, rather than being kept in the dark.\u201d\n\nThe researcher says attackers would have to change the name of a HomeKit device to large strings of up to 500,000 characters and trick the target into accepting a Home invitation.\n\nOnce the target joins the attacker\u2019s HomeKit network, their device becomes unresponsive and eventually crashes.\n\nThe only way to recover from such an attack would be to factory reset the disabled device, given that it will once again crash after restarting and signing back into the iCloud account linked to the HomeKit device.\nSee Also: Offensive Security Tool: Osmedeus Zero-day patches\u00a0also delayedIn September, software developer\u00a0Denis Tokarev also dropped\u00a0proof-of-concept exploit code for three iOS zero-day flaws\u00a0on GitHub after Apple delayed patching and failed to credit him when patching a fourth in July.\n\nOne month later, with the release of iOS 15.0.2, Apple\u00a0fixed one of the\u00a0\u2018gamed\u2019 zero-day vulnerabilities reported by Tokarev.\n\nHowever, Apple didn\u2019t\u00a0acknowledge or credit\u00a0him for the discovery and also asked him to keep quiet\u00a0and not disclose to others that the company failed to give him credit for the bug.\n\nOther security researchers and bug bounty hunters\u00a0have also gone through\u00a0similar experiences saying\u00a0th[...]\n\n___________________________ \n@hacking_Attack\n@Hacking_Video", "creation_timestamp": "2026-09-01T20:01:59.724373Z"}