{"uuid": "ac7e2421-434c-4139-beb2-93de41f6aefb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-28206", "type": "seen", "source": "https://t.me/hacking_Attack/117671", "content": "Black Hat Ethical Hacking\nEmergency Apple Updates: Zero-Days Exploited to Deploy Spyware on iPhones\n\nEmergency Apple Updates: Zero-Days Exploited to Deploy Spyware on iPhones\nPost Views: 1 Premium Content https://www.blackhatethicalhacking.com/wp-content/uploads/2023/07/Patreon.png Subscribe to Patreon to watch this episode.\nReading Time: 3 Minutes\nApple issued emergency security updates to address two zero-day vulnerabilities that were actively exploited in a sophisticated zero-click exploit chain. These vulnerabilities served as entry points for deploying NSO Group\u2019s Pegasus commercial spyware onto fully patched iPhones.\n\nThe two identified vulnerabilities, tracked as CVE-2023-41064 and CVE-2023-41061, allowed attackers to compromise iPhones running iOS 16.6, even if they were fully patched. This alarming breach occurred within a Washington DC-based civil society organization through PassKit attachments containing malicious images.\n\nCitizen Lab, a prominent research organization, has named this exploit chain \u201cBLASTPASS.\u201d The concerning aspect of this attack is that it could compromise iPhones running the latest version of iOS (16.6) without requiring any interaction from the victim. The attack method involved PassKit attachments, containing malicious images, sent from the attacker\u2019s iMessage account to the victim\u2019s device.\n\nIn response to these critical security breaches, Citizen Lab strongly advises all Apple customers to update their devices immediately. Furthermore, individuals who may be at risk of targeted attacks due to their identity or profession are encouraged to activate Lockdown Mode on their devices.\nWe refer to the exploit as BLASTPASS, as it employed a PassKit (Wallet) attachment containing a malicious image, sent via iMessage. When the phone processed the attachment, the exploit hijacked control of Apple's \"BlastDoor\" framework for iMessage security.\n\n\u2014 Bill Marczak (@billmarczak) September 7, 2023\nSee Also: So you want to be a hacker? Offensive Security, Bug Bounty Courses\nThese two zero-day vulnerabilities were discovered by both Apple and security researchers at Citizen Lab. They were found to exist within the Image I/O and Wallet frameworks.\n\nCVE-2023-41064 is characterized as a buffer overflow vulnerability, triggered during the processing of maliciously crafted images. On the other hand, CVE-2023-41061 is a validation issue that can be exploited via malicious attachments. Both of these vulnerabilities allowed threat actors to gain arbitrary code execution on unpatched iPhone and iPad devices.\n\nApple has promptly addressed these flaws through updates, including macOS Ventura 13.5.2, iOS 16.6.1, iPadOS 16.6.1, and watchOS 9.6.2. These updates incorporate improved logic and memory handling to mitigate the vulnerabilities.\n\nA range of Apple devices were affected, including iPhone 8 and later models, various iPad models, Macs running macOS Ventura, and Apple Watch Series 4 and later.\nTrending: The Remarkable Journey of Dave Kennedy as a Cyber Security Innovator Trending: Recon Tool: Dirhunt This marks the 13th zero-day vulnerability that Apple has addressed since the beginning of the year. \nThese vulnerabilities have been exploited to target devices running iOS, macOS, iPadOS, and watchOS. Apple\u2019s commitment to swiftly patching such vulnerabilities underscores its dedication to user security.\n\n* In July, two zero-days (CVE-2023-37450 and CVE-2023-38606) were addressed\n* June saw the fixing of three zero-days (CVE-2023-32434, CVE-2023-32435, and CVE-2023-32439).\n* May brought three additional zero-days (CVE-2023-32409, CVE-2023-28204, and CVE-2023-32373)\n* April saw the resolution of two zero-days (CVE-2023-28206 and CVE-2023-28205).\n* In February, another WebKit z[...]", "creation_timestamp": "2026-09-01T20:00:51.612313Z"}