311 matches found
CVE-2026-11117-WPA2-4-Way-Handshake-Reinstallation-KRACK-Sim-
CVE-2026-11117 – Reinstalación del handshake de 4 vías en WPA2 Simulación de KRACK Código del programa Python root@kitploit: kracksim.py - Simulates reinstallation of an already-used PTK import hashlib, os class AccessPoint: def initself: self.anonce = os.urandom32 self.ptk = None def sendmsg3sel...
CVE-2026-11110-AES-GCM-Nonce-Reuse-Leading-to-Key-Recovery
CVE-2026-11110 – Reutilización de Nonce en AES-GCM que Conduce a la Recuperación de Claves Código del Programa Python root@kitploit: aesgcmnoncereusesim.py - Simulated encryption oracle with fixed nonce from Crypto.Cipher import AES import os key = os.urandom16 nonce = b'\x00' 12 ALWAYS SAME NONC...
CVE-2026-21009-ECDSA-Nonce-Reuse-in-IoT-Firmware-Signing
CVE-2026-21009 – Reutilización de nonce ECDSA en el firmado de firmware IoT Código del programa Python root@kitploit: ecdsanoncereusesim.py - Signing firmware with repeated nonce k import ecdsa, hashlib sk = ecdsa.SigningKey.generatecurve=ecdsa.NIST256p vk = sk.getverifyingkey Sign two different...
CVE-2026-21010-VoIP-SIP-Digest-Authentication-Replay
CVE-2026-21010 – Replay de autenticación digest SIP en VoIP Código del programa simulador SIP en Python root@kitploit: sipserversim.py - SIP server that accepts replayed authenticated requests from flask import Flask, request app = Flaskname Simulated nonce storage: doesn't track used nonces...
CVE-2026-88278
GeoVision GV-LPC2211 V1.13 fails to enforce WS-Security UsernameToken freshness or nonce reuse protection, allowing a captured PasswordDigest token to be replayed for subsequent ONVIF operations...
EUVD-2026-75312
GeoVision GV-LPC2211 V1.13 fails to enforce WS-Security UsernameToken freshness or nonce reuse protection, allowing a captured PasswordDigest token to be replayed for subsequent ONVIF operations...
CVE-2026-22001-SPHINCS-WOTS-Weak-Randomness-Forgeable-Signature
CVE-2026-22001 – Falsificación de Firmas por Aleatoriedad Débil en WOTS+ de SPHINCS+ Resumen Una implementación del esquema de firmas post-cuánticas SPHINCS+ utiliza un generador de números aleatorios defectuoso durante la generación de firmas WOTS+. El mismo nonce k se reutiliza en múltiples...
CVE
CVE Informes de CVE-2025-67586, CVE-2025-67985, CVE-2025-67986 root@kitploit: -------------- CVE-2025-67586 Exploit PoC -------------- Título del Exploit: WordPress Plugin 5.2.0 - Control de Acceso Roto Enlace del software: https://wordpress.org/plugins/highlight-and-share/ Versión: Descripción...
ecdsa-private-key-recovery
ecdsa-key-recovery Realiza ataques de recuperación de clave privada por reutilización de nonce en ECDSA y DSA Una herramienta de investigación criptográfica para analizar vulnerabilidades en firmas Vamos a recuperar la clave privada de dos firmas que comparten el mismo nonce k. Observa cómo elegi...
ecdsa-private-key-recovery
ecdsa-key-recovery Perform ECDSA and DSA Nonce Reuse private key recovery attacks A cryptographic research tool for analyzing signature vulnerabilities Let's recover the private-key for two signatures sharing the same nonce k. Note how choosing the same nonce k results in both signatures having a...
CVE-2026-81341
wolfEngine before 1.4.1 sources the explicit AES-CCM nonce for TLS 1.2 and DTLS 1.2 records from the record input buffer instead of the TLS sequence number carried in the additional authenticated data. Because the record layer leaves the explicit-nonce field for the cipher to populate, the value...
CVE-2026-81020
wolfEngine before 1.4.1 generates the 8-byte explicit AES-GCM nonce once when the TLS write key is set and never increments it per record. As a result every TLS 1.2 and DTLS 1.2 AES-GCM record within a connection is encrypted under an identical key and nonce pair. Reusing a GCM key and nonce...
CVE-2026-81019
wolfProvider before 1.2.2 generates the 8-byte explicit AES-GCM nonce once when the TLS write key is set and never increments it per record. As a result every TLS 1.2 and DTLS 1.2 AES-GCM record within a connection is encrypted under an identical key and nonce pair. Reusing a GCM key and nonce...
CVE-2026-81341 wolfEngine reuses the AES-CCM nonce on TLS 1.2 / DTLS 1.2 records
wolfEngine before 1.4.1 sources the explicit AES-CCM nonce for TLS 1.2 and DTLS 1.2 records from the record input buffer instead of the TLS sequence number carried in the additional authenticated data. Because the record layer leaves the explicit-nonce field for the cipher to populate, the value...
CVE-2026-81341
wolfEngine (before 1.4.1 ) reuses the AES-CCM nonce on TLS 1.2 and DTLS 1.2 records because it sources the explicit nonce from the record input buffer rather than the TLS sequence number. Since the record layer leaves that field for the cipher to populate, the value is constant, meaning every AES...
CVE-2026-81341 wolfEngine reuses the AES-CCM nonce on TLS 1.2 / DTLS 1.2 records
wolfEngine before 1.4.1 sources the explicit AES-CCM nonce for TLS 1.2 and DTLS 1.2 records from the record input buffer instead of the TLS sequence number carried in the additional authenticated data. Because the record layer leaves the explicit-nonce field for the cipher to populate, the value...
EUVD-2026-67738
wolfEngine before 1.4.1 sources the explicit AES-CCM nonce for TLS 1.2 and DTLS 1.2 records from the record input buffer instead of the TLS sequence number carried in the additional authenticated data. Because the record layer leaves the explicit-nonce field for the cipher to populate, the value...
CVE-2026-81020 wolfEngine reuses the AES-GCM nonce on every TLS 1.2 / DTLS 1.2 record
wolfEngine before 1.4.1 generates the 8-byte explicit AES-GCM nonce once when the TLS write key is set and never increments it per record. As a result every TLS 1.2 and DTLS 1.2 AES-GCM record within a connection is encrypted under an identical key and nonce pair. Reusing a GCM key and nonce...
EUVD-2026-67737
wolfEngine before 1.4.1 generates the 8-byte explicit AES-GCM nonce once when the TLS write key is set and never increments it per record. As a result every TLS 1.2 and DTLS 1.2 AES-GCM record within a connection is encrypted under an identical key and nonce pair. Reusing a GCM key and nonce...
CVE-2026-81020
wolfEngine before 1.4.1 generates the 8-byte explicit AES-GCM nonce only once when the TLS write key is set and never increments it per record. Consequently, every TLS 1.2 and DTLS 1.2 AES-GCM record within a connection is encrypted under an identical key and nonce pair. GCM nonce reuse discloses...