Davidsclee

The Tapo Cloud MQTT broker contains a broken access control vulnerability in a proxy topic used by authenticated Tapo devices to request service tokens. The broker does not verify that the device ID supplied in a proxy request belongs to the authenticated device. An attacker who owns a Tapo device and knows another device's ID may obtain a device token scoped to the target device and use it to upload attacker-controlled content to the target user's Tapo Cloud storage. The content may then be presented in the Tapo app as a legitimate event. Successful exploitation may allow an attacker to upload attacker-controlled content that is presented to a target user as a legitimate Tapo event, retrieve internal service information through crafted proxy requests, or abuse Tapo Cloud outbound request capability in activity that could affect service availability.

The Tapo Cloud MQTT proxy contains a server-side request forgery (SSRF) vulnerability because it accepts a user-controlled host value without sufficient input validation. An attacker may exploit this vulnerability to cause the Tapo Cloud service to send requests to an attacker-controlled server. Successful exploitation may cause the Tapo Cloud service to send a request to an attacker-controlled server, exposing the internal information and causing potential Distributed Denial-of-Service (DDoS).

Um estouro de buffer baseado em heap ocorre na lógica de análise do corpo HTTP POST devido à validação de limites insuficiente e à falta de validação da capacidade restante do buffer após a alocação dinâmica ao lidar com entradas HTTP fornecidas externamente. Um atacante no mesmo segmento de rede pode desencadear a corrupção de memória do heap enviando cargas úteis manipuladas que causam operações de escrita além dos limites do buffer alocado. A exploração bem-sucedida pode levar a uma condição de Negação de Serviço (DoS), fazendo com que o processo do dispositivo trave ou pare de responder, ou potencialmente permitir a execução remota de código (RCE).