Page 2 of 26 results (0.004 seconds)

CVSS: 5.9EPSS: 0%CPEs: 1EXPL: 1

Botan 2.5.0 through 2.6.0 before 2.7.0 allows a memory-cache side-channel attack on ECDSA signatures, aka the Return Of the Hidden Number Problem or ROHNP, related to dsa/dsa.cpp, ec_group/ec_group.cpp, and ecdsa/ecdsa.cpp. To discover an ECDSA key, the attacker needs access to either the local machine or a different virtual machine on the same physical host. Botan versión 2.5.0 hasta 2.6.0 anterior a 2.7.0, permite un ataque de canal lateral de memoria caché en firmas ECDSA, también se conoce como Problema del Retorno de Número Oculto o ROHNP, relacionado con los archivos dsa/dsa.cpp, ec_group/ec_group.cpp, y ecdsa/ecdsa.cpp. Para descubrir una clave ECDSA, el atacante requiere acceso a la máquina local o a una máquina virtual diferente en el mismo host físico. • https://botan.randombit.net/security.html https://github.com/randombit/botan/commit/48fc8df51d99f9d8ba251219367b3d629cc848e3 https://www.nccgroup.trust/us/our-research/technical-advisory-return-of-the-hidden-number-problem • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor •

CVSS: 7.5EPSS: 0%CPEs: 1EXPL: 0

An issue was discovered in Botan 1.11.32 through 2.x before 2.6.0. An off-by-one error when processing malformed TLS-CBC ciphertext could cause the receiving side to include in the HMAC computation exactly 64K bytes of data following the record buffer, aka an over-read. The MAC comparison will subsequently fail and the connection will be closed. This could be used for denial of service. No information leak occurs. • https://botan.randombit.net/security.html https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=7434 • CWE-193: Off-by-one Error •

CVSS: 9.8EPSS: 0%CPEs: 1EXPL: 0

Botan 2.2.0 - 2.4.0 (fixed in 2.5.0) improperly handled wildcard certificates and could accept certain certificates as valid for hostnames when, under RFC 6125 rules, they should not match. This only affects certificates issued to the same domain as the host, so to impersonate a host one must already have a wildcard certificate matching other hosts in the same domain. For example, b*.example.com would match some hostnames that do not begin with a 'b' character. Botan 2.2.0 - 2.4.0 (solucionado en 2.5.0) gestionaba de manera incorrecta certificados wildcard y podría aceptar determinados certificados como válidos para nombres de hosts cuando, bajo las reglas RFC 6125, no deberían coincidir. Esto solo afecta a certificados emitidos al mismo dominio que el host, por lo que para suplantar un host el certificado wildcard tiene que coincidir con otros hosts en el mismo dominio. • https://botan.randombit.net/security.html • CWE-295: Improper Certificate Validation •

CVSS: 5.5EPSS: 0%CPEs: 37EXPL: 0

A cryptographic cache-based side channel in the RSA implementation in Botan before 1.10.17, and 1.11.x and 2.x before 2.3.0, allows a local attacker to recover information about RSA secret keys, as demonstrated by CacheD. This occurs because an array is indexed with bits derived from a secret key. Un canal lateral criptográfico basado en caché en la implementación RSA en Botan en versiones anteriores a la 1.10.17 y las versiones 1.11.x y 2.x anteriores a la 2.3.0 permite que un atacante local recupere información sobre las claves secretas RSA, tal y como demuestra CacheD. Esto ocurre porque un array se indexa con bits derivados de una clave secreta. • https://github.com/randombit/botan/issues/1222 https://lists.debian.org/debian-lts-announce/2021/11/msg00006.html https://www.usenix.org/conference/usenixsecurity17/technical-sessions/presentation/wang-shuai •

CVSS: 9.8EPSS: 0%CPEs: 1EXPL: 1

A programming error exists in a way Randombit Botan cryptographic library version 2.0.1 implements x500 string comparisons which could lead to certificate verification issues and abuse. A specially crafted X509 certificate would need to be delivered to the client or server application in order to trigger this vulnerability. Existe un error de programación en una manera en que la biblioteca criptográfica Randombit Botan versión 2.0.1, implementa comparaciones de cadenas x500 que podrían conllevar problemas de comprobación de certificados y violarlos. Un certificado X509 especialmente diseñado debería entregarse al cliente o a la aplicación del servidor para desencadenar esta vulnerabilidad. • http://talosintelligence.com/vulnerability_reports/TALOS-2017-0294 http://www.debian.org/security/2017/dsa-3939 http://www.securityfocus.com/bid/98106 • CWE-125: Out-of-bounds Read •