Falhas do tipo CWE-1300

35 resultados

Vazamento de informações por canal secundário

É quando dados sensíveis vazam não pela entrada/saída principal do programa, mas por canais indiretos como tempo de execução, consumo de energia, emissões eletromagnéticas ou comportamento de cache. O atacante observa essas características físicas ou de timing para inferir segredos criptográficos, senhas ou dados confidenciais sem quebrar a lógica de segurança do código.

Exemplo

Uma função de validação de senha que compara byte a byte pode vazar o comprimento ou quantos caracteres estão corretos através do tempo de execução: se a comparação falha no 3º caractere, levará menos tempo do que se falhasse no 10º, permitindo ao atacante adivinhar senha iterativamente.

Como mitigar

Use comparações em tempo constante (funções como `crypto.timingSafeEqual` em Node.js ou `hmac_equals` em PHP), implemente mascaramento de operações sensíveis, adicione delays aleatórios, e considere proteções de hardware contra análise de potência em ambientes críticos. Teste e valide a ausência de padrões de timing correlacionados com dados secretos.

CVE-2025-11210MEDIUMSide-channel information leakage in Tab in Google Chrome prior to 141.0.7390.54 allowed a remote attacker who convinced a user to engage in EPSS 0.2%CVE-2026-17914MEDIUMSide-channel information leakage in Skia in Google Chrome prior to 151.0.7922.72 allowed a remote attacker to obtain potentially sensitive iEPSS 0.2%CVE-2026-17978MEDIUMSide-channel information leakage in WebCodecs in Google Chrome prior to 151.0.7922.72 allowed a remote attacker to obtain potentially sensitEPSS 0.2%CVE-2026-14012MEDIUMSide-channel information leakage in CSS in Google Chrome prior to 150.0.7871.47 allowed a remote attacker to obtain potentially sensitive inEPSS 0.2%CVE-2026-17942MEDIUMSide-channel information leakage in SVG in Google Chrome prior to 151.0.7922.72 allowed a remote attacker to leak cross-origin data via a crEPSS 0.2%CVE-2026-17802MEDIUMSide-channel information leakage in GPU in Google Chrome on Android prior to 151.0.7922.72 allowed a remote attacker to leak cross-origin daEPSS 0.2%CVE-2026-11289MEDIUMSide-channel information leakage in Paint in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to leak cross-origin data via a EPSS 0.2%CVE-2026-17907MEDIUMSide-channel information leakage in Network in Google Chrome prior to 151.0.7922.72 allowed a remote attacker to leak cross-origin data via EPSS 0.2%CVE-2026-8562MEDIUMSide-channel information leakage in Navigation in Google Chrome prior to 148.0.7778.168 allowed a remote attacker to leak cross-origin data EPSS 0.2%CVE-2025-13992MEDIUMSide-channel information leakage in Navigation and Loading in Google Chrome prior to 139.0.7258.66 allowed a remote attacker to bypass site EPSS 0.2%CVE-2026-3929LOWSide-channel information leakage in ResourceTiming in Google Chrome prior to 146.0.7680.71 allowed a remote attacker to leak cross-origin daEPSS 0.2%CVE-2026-18019MEDIUMSide-channel information leakage in Media in Google Chrome prior to 151.0.7922.72 allowed a remote attacker to leak cross-origin data via a EPSS 0.2%CVE-2026-8017LOWSide-channel information leakage in Media in Google Chrome prior to 148.0.7778.96 allowed a remote attacker to leak cross-origin data via a EPSS 0.1%CVE-2026-6923LOWNuvoton - CWE-1300: Improper Protection of Physical Side ChannelsEPSS 0.1%CVE-2026-0115LOWIn Trusted Execution Environment, there is a possible key leak due to side channel information disclosure. This could lead to physical inforEPSS 0.1%