Bill Marczak

Esta correção aborda uma falha de autorização com gerenciamento de estado aprimorado. Um ataque físico pode desativar o Modo Restrito de USB em um dispositivo bloqueado. A Apple está ciente de relatos indicando que esta vulnerabilidade pode ter sido explorada em ataques altamente sofisticados visando indivíduos específicos. A vulnerabilidade permite que invasores com acesso físico contornem o Modo Restrito de USB, possibilitando potencialmente a extração de dados de dispositivos bloqueados. Foi relatado que ela foi explorada em ataques direcionados.

A certificate validation issue exists in Apple’s CoreTrust security component, potentially allowing malicious applications to bypass signature validation. Reports indicate that this issue may have been actively exploited against versions of iOS prior to version 16.7. The CoreTrust vulnerability, identified as CVE-2023-41991, was reportedly exploited by commercial surveillance vendors, including Intellexa and NSO Group, to install malicious software on iPhones. The issue involves incorrect validation of apps with multiple signers, allowing attackers to circumvent normal signature checks. This flaw was used in conjunction with other vulnerabilities, such as local privilege escalation and remote code execution. The exploit was significant enough that Apple released patches in iOS versions 16.7 and 17.0.1, as well as macOS Ventura 13.6, watchOS 9.6.3, and watchOS 10.0.1 to address the vulnerability.

The issue involves insufficient checks when processing web content within the kernel of iOS, watchOS, iPadOS, and macOS, potentially allowing an attacker to elevate their privileges. Reports indicate that this issue may have been actively exploited in versions of iOS prior to iOS 16.7. The vulnerability allows malicious applications to bypass signature validation and gain elevated privileges. The issue was addressed by implementing improved checks. The vulnerability affects multiple Apple platforms. Technical details reveal the exploitation involves triggering a bug on an old thread, invoking `ipc entry grow table()` through `mach port allocate name()`, and subsequently calling `mach thread self()` to obtain a new mach name.

A vulnerability exists in the WebKit engine, potentially allowing attackers to execute arbitrary code by processing malicious web content. This issue has been actively exploited in some instances, with reports indicating exploitation against iOS versions prior to 16.7. The vulnerability was addressed through improved checks in updated versions of the software. A threat actor, linked to Russia’s Foreign Intelligence Service (SVR), leveraged this vulnerability (CVE-2023-41993) in a watering hole campaign, compromising legitimate websites and redirecting visitors to malicious login pages to harvest Microsoft 365 credentials. Intellexa, a spyware vendor, also utilized this vulnerability as part of a zero-day exploit chain to deploy the Predator spyware on targets in Egypt. The exploit chain involved multiple zero-day vulnerabilities, including CVE-2023-41993, to gain deep access to devices.

O problema diz respeito ao uso do modo ECB do AES para criptografia, o que pode revelar informações estruturais sobre mensagens criptografadas. No caso do Zoom Client for Meetings, todos os participantes de uma reunião utilizam uma única chave de 128 bits para criptografia de vídeo e áudio. Da mesma forma, a criptografia de mensagens do Microsoft Office 365 utiliza o modo ECB, permitindo que invasores possam determinar o conteúdo das mensagens criptografadas por meio da análise de padrões. Esse problema já havia sido identificado em 2013 e novamente em 2020. Foi relatado que a Microsoft está ciente do problema desde janeiro de 2022, mas ainda não lançou uma correção, embora esteja trabalhando para adicionar um protocolo de criptografia alternativo às futuras versões do produto.