Botan Project vulnerabilities, page 2

35 vulnerabilities

Known vulnerabilities in Botan Project products, newest first, with CVSS severity, EPSS, KEV listings and ransomware use, across 1 product.

6.2MediumCVE-2016-8871botan_project · botanbotan_project botanIn Botan 1.11.29 through 1.11.32, RSA decryption with certain padding options had a detectable timing channel which could given sufficient queries be used to recover plaintext, aka an "OAEP side channel" attack.EPSS0.41%7.5HighCVE-2014-9742botan_project · botan +1 morebotan_project botanThe Miller-Rabin primality check in Botan before 1.10.8 and 1.11.x before 1.11.9 improperly uses a single random base, which makes it easier for remote attackers to defeat cryptographic protection mechanisms via a DH group.EPSS1.43%9.1CriticalCVE-2022-43705botan_project · botan +8 morebotan_project botanIn Botan before 2.19.3, it is possible to forge OCSP responses due to a certificate verification error. This issue was introduced in Botan 1.11.34 (November 2016).EPSS0.45%9.8CriticalCVE-2017-2801botan_project · botan +4 morebotan_project botanA 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.EPSS1.32%5.5MediumCVE-2017-14737botan_project · botan +7 morebotan_project botanA 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.EPSS0.32%7.5HighCVE-2017-7252botan_project · botanbotan_project botanbcrypt password hashing in Botan before 2.1.0 does not correctly handle passwords with a length between 57 and 72 characters, which makes it easier for attackers to determine the cleartext password.EPSS0.32%5.3MediumCVE-2024-39312Alpine Linuxalpine · botan +5 moreBotan has an Authorization Error due to Name Constraint Decoding BugBotan is a C++ cryptography library. X.509 certificates can identify elliptic curves using either an object identifier or using explicit encoding of the parameters. A bug in the parsing of name constraint extensions in X.509 certificates meant that if the extension included both permitted subtrees and excluded subtrees, only the permitted subtree would be checked. If a certificate included a name which was permitted by the permitted subtree but also excluded by excluded subtree, it would be accepted. Fixed in versions 3.5.0 and 2.19.5.EPSS0.27%5.9MediumCVE-2024-50382botan_project · botan +4 morebotan_project botanBotan before 3.6.0, when certain LLVM versions are used, has compiler-induced secret-dependent control flow in lib/utils/ghash/ghash.cpp in GHASH in AES-GCM. There is a branch instead of an XOR with carry. This was observed for Clang in LLVM 15 on RISC-V.EPSS0.55%5.9MediumCVE-2024-50383botan_project · botan +4 morebotan_project botanBotan before 3.6.0, when certain GCC versions are used, has a compiler-induced secret-dependent operation in lib/utils/donna128.h in donna128 (used in Chacha-Poly1305 and x25519). An addition can be skipped if a carry is not set. This was observed for GCC 11.3.0 with -O2 on MIPS, and GCC on x86-i386. (Only 32-bit processors can be affected.)EPSS0.55%7.5HighCVE-2026-44378botan_project · botan +4 moreBotan: Quadratic complexity decoding BER indefinite length encodingsBotan is a C++ cryptography library. Prior to 3.12.0, certain patterns of indefinite length encodings in BER data could cause quadratic behavior in the parser, resulting in a denial of service. Such BER encodings were accepted even in structures which are required to be encoded as DER, which prohibits indefinite length encodings. This vulnerability is fixed in 3.12.0.EPSS0.46%5.9MediumCVE-2026-32884Alpine Linuxalpine · botan3 +8 moreBotan: Case-Insensitive CN Values Bypass DNS excludedSubtrees Name Constraints (RFC 5280 Violation)Botan is a C++ cryptography library. Prior to version 3.11.0, during processing of an X.509 certificate path using name constraints which restrict the set of allowable DNS names, if no subject alternative name is defined in the end-entity certificate Botan would check that the CN was allowed by the DNS name constraints, even though this check is technically not required by RFC 5280. However this check failed to account for the possibility of a mixed-case CN. Thus a certificate with CN=Sub.EVIL.COM and no subject alternative name would bypasses an excludedSubtrees constraint for evil.com because the comparison is case-sensitive. This issue has been patched in version 3.11.0.EPSS0.20%5.9MediumCVE-2026-32883Alpine Linuxalpine · botan3 +6 moreBotan: Missing OCSP Response Signature Verification Allows MitM Certificate Revocation BypassBotan is a C++ cryptography library. From version 3.0.0 to before version 3.11.0, during X509 path validation, OCSP responses were checked for an appropriate status code, but critically omitted verifying the signature of the OCSP response itself. This issue has been patched in version 3.11.0.EPSS0.19%8.2HighCVE-2026-32877Alpine Linuxalpine · botan3 +7 moreBotan: Heap Buffer Over-read in SM2 Decryption via Undersized C3 Hash FieldBotan is a C++ cryptography library. From version 2.3.0 to before version 3.11.0, during SM2 decryption, the code that checked the authentication code value (C3) failed to check that the encoded value was of the expected length prior to comparison. An invalid ciphertext can cause a heap over-read of up to 31 bytes, resulting in a crash or potentially other undefined behavior. This issue has been patched in version 3.11.0.EPSS0.50%9.3CriticalCVE-2026-34580Alpine Linuxalpine · botan3 +4 moreBotan has a certificate authentication bypass due to trust anchor confusionBotan is a C++ cryptography library. In 3.11.0, the function Certificate_Store::certificate_known had a misleading name; it would return true if any certificate in the store had a DN (and subject key identifier, if set) matching that of the argument. It did not check that the cert it found and the cert it was passed were actually the same certificate. In 3.11.0 an extension of path validation logic was made which assumed that certificate_known only returned true if the certificates were in fact identical. The impact is that if an end entity certificate is presented, and its DN (and subject key identifier, if set) match that of any trusted root, the end entity certificate is accepted immediately as if it itself were a trusted root. , This vulnerability is fixed in 3.11.1.EPSS0.32%9.1CriticalCVE-2026-34582Alpine Linuxalpine · botan3 +6 moreBotan has a TLS 1.3 certificate authentication bypassBotan is a C++ cryptography library. Prior to version 3.11.1, the TLS 1.3 implementation allowed ApplicationData records to be processed prior to the Finished message being received. A server which is attempting to enforce client authentication via certificates can by bypassed by a client which entirely omits Certificate, CertificateVerify, and the Finished message and instead sends application data records. This vulnerability is fixed in 3.11.1.EPSS0.38%