Weaknesses of type CWE-1300

35 results

Vazamento de informações por canal secundário

É quando o sistema vaza dados sensíveis não pelos dados em si, mas por sinais indiretos como tempo de execução, consumo de energia, ruído eletromagnético ou padrões de acesso à memória. Um atacante observa essas características físicas ou comportamentais para inferir segredos (senhas, chaves criptográficas) sem quebrar a criptografia.

Example

Uma função que valida senha comparando byte a byte pode variar o tempo de resposta conforme quantos caracteres estão corretos: atacante tira vantagem dessa diferença de milissegundos para adivinhar a senha. Outro caso: um servidor que processa requisições usa mais energia/CPU ao processar uma chave correta versus incorreta, e alguém monitora via osciloscópio.

How to mitigate

Use operações de tempo constante (constant-time) para comparações sensíveis; implemente mascaramento e aleatorização nos cálculos criptográficos; evite padrões previsíveis de acesso à memória; quando possível, ofusque o timing e o consumo de recursos. Testes de timing e análise de potência durante code review ajudam a identificar.

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%