Botanproject Botan
By the Year
In 2024 there have been 0 vulnerabilities in Botanproject Botan . Last year Botan had 1 security vulnerability published. Right now, Botan is on track to have less security vulnerabilities in 2024 than it did last year.
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2024 | 0 | 0.00 |
| 2023 | 1 | 7.50 |
| 2022 | 1 | 9.10 |
| 2021 | 2 | 7.85 |
| 2020 | 0 | 0.00 |
| 2019 | 1 | 5.90 |
| 2018 | 3 | 7.73 |
It may take a day or so for new Botan vulnerabilities to show up in the stats or in the list of recent security vulnerabilties. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Botanproject Botan Security Vulnerabilities
bcrypt password hashing in Botan before 2.1.0 does not correctly handle passwords with a length between 57 and 72 characters
CVE-2017-7252
7.5 - High
- November 03, 2023
bcrypt 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.
Cleartext Transmission of Sensitive Information
In Botan before 2.19.3, it is possible to forge OCSP responses due to a certificate verification error
CVE-2022-43705
9.1 - Critical
- November 27, 2022
In 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).
Improper Certificate Validation
The ElGamal implementation in Botan through 2.18.1, as used in Thunderbird and other products
CVE-2021-40529
5.9 - Medium
- September 06, 2021
The ElGamal implementation in Botan through 2.18.1, as used in Thunderbird and other products, allows plaintext recovery because, during interaction between two cryptographic libraries, a certain dangerous combination of the prime defined by the receiver's public key, the generator defined by the receiver's public key, and the sender's ephemeral exponents can lead to a cross-configuration attack against OpenPGP.
Use of a Broken or Risky Cryptographic Algorithm
In Botan before 2.17.3
CVE-2021-24115
9.8 - Critical
- February 22, 2021
In Botan before 2.17.3, constant-time computations are not used for certain decoding and encoding operations (base32, base58, base64, and hex).
A side-channel issue was discovered in Botan before 2.9.0
CVE-2018-20187
5.9 - Medium
- March 08, 2019
A side-channel issue was discovered in Botan before 2.9.0. An attacker capable of precisely measuring the time taken for ECC key generation may be able to derive information about the high bits of the secret key, as the function to derive the public point from the secret scalar uses an unblinded Montgomery ladder whose loop iteration count depends on the bitlength of the secret. This issue affects only key generation, not ECDSA signatures or ECDH key agreement.
Key Management Errors
Botan 2.5.0 through 2.6.0 before 2.7.0
CVE-2018-12435
5.9 - Medium
- June 15, 2018
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.
Information Disclosure
An issue was discovered in Botan 1.11.32 through 2.x before 2.6.0
CVE-2018-9860
7.5 - High
- April 12, 2018
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.
off-by-five
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
CVE-2018-9127
9.8 - Critical
- April 02, 2018
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.
Improper Certificate Validation
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
CVE-2017-14737
5.5 - Medium
- September 26, 2017
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.
A programming error exists in a way Randombit Botan cryptographic library version 2.0.1 implements x500 string comparisons
CVE-2017-2801
9.8 - Critical
- May 24, 2017
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.
Out-of-bounds Read
Stay on top of Security Vulnerabilities
Want an email whenever new vulnerabilities are published for Botanproject Botan or by Botanproject? Click the Watch button to subscribe.
