Falhas do tipo CWE-208

212 resultados

Discrepância de Tempo Observável

É quando um programa leva tempos diferentes para processar entradas válidas versus inválidas, e esse tempo é observável por um atacante. Essa variação permite inferir informações sensíveis (como senhas ou tokens) através de ataques de timing, sem acesso direto aos dados.

Exemplo

Uma função que compara uma senha caractere por caractere, saindo assim que encontra um erro, leva menos tempo para senhas erradas no início do que para senhas quase corretas. Um atacante mede os tempos de resposta da API e descobre a senha testando caracteres até encontrar aquele que aumenta o tempo de processamento.

Como mitigar

Use comparação em tempo constante (funções como `hmac.compare()` em Node.js ou `secrets.compare()` em Python) que sempre levam o mesmo tempo independente da entrada. Adicione jitter (variação aleatória) no tempo de resposta e implemente rate limiting para dificultar medições precisas.

CVE-2025-53940HIGHQuiet uses insecure, inconsistent verification on local backend tokenEPSS 4.2%CVE-2019-9494—The implementations of SAE in hostapd and wpa_supplicant are vulnerable to side-channel attacksEPSS 3.9%CVE-2019-16782MEDIUMPossible Information Leak / Session Hijack Vulnerability in RackEPSS 3.7%CVE-2020-1926—Timing attack in Cookie signature verificationEPSS 2.5%CVE-2021-43298—The code that performs password matching when using 'Basic' HTTP authentication does not use a constant-time memcmp and has no rate-limitingEPSS 2.3%CVE-2022-31142HIGHPotential Timing Attack Vector in @fastify/bearer-authEPSS 1.5%CVE-2024-29995HIGHWindows Kerberos Elevation of Privilege VulnerabilityEPSS 1.5%CVE-2024-23953MEDIUMApache Hive: Timing Attack Against Signature in LLAP utilEPSS 1.4%CVE-2016-10535—csrf-lite is a cross-site request forgery protection library for framework-less node sites. csrf-lite uses `===`, a fail first string comparEPSS 1.3%CVE-2023-5981MEDIUMGnutls: timing side-channel in the rsa-psk authenticationEPSS 1.3%CVE-2026-47783HIGHIn memcached before 1.6.42, username data for SASL password database authentication has a timing side channel because a loop exits as soon aEPSS 1.3%CVE-2024-54772MEDIUMAn issue was discovered in the Winbox service of MikroTik RouterOS long-term release v6.43.13 through v6.49.13 and stable v6.43 through v7.1EPSS 1.2%CVE-2019-13420—Search Guard versions before 21.0 had an timing side channel issue when using the internal user database.EPSS 1.2%CVE-2026-3337HIGHTiming Side-Channel in AES-CCM Tag Verification in AWS-LCEPSS 1.1%CVE-2022-20752MEDIUMCisco Unified Communications Products Timing Attack VulnerabilityEPSS 1.1%CVE-2023-41313CRITICALApache Doris: Timing Attack weaknessEPSS 1.1%CVE-2020-15237MEDIUMTiming attack in ShrineEPSS 1.0%CVE-2024-23342HIGHpython-ecdsa vulnerable to Minerva attack on P-256EPSS 1.0%CVE-2010-10006LOWmichaelliao jopenid OpenIdManager.java getAuthentication timing discrepancyEPSS 0.9%CVE-2024-39329MEDIUMAn issue was discovered in Django 5.0 before 5.0.7 and 4.2 before 4.2.14. The django.contrib.auth.backends.ModelBackend.authenticate() methoEPSS 0.9%