Vulnerabilities > Botan Project
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2017-05-24 | CVE-2017-2801 | Out-of-bounds Read vulnerability in Botan Project Botan 2.0.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. | 9.8 |
| 2017-04-10 | CVE-2016-6879 | Key Management Errors vulnerability in Botan Project Botan The X509_Certificate::allowed_usage function in botan 1.11.x before 1.11.31 might allow attackers to have unspecified impact by leveraging a call with more than one Key_Usage set in the enum value. | 7.5 |
| 2017-04-10 | CVE-2016-6878 | Improper Input Validation vulnerability in Botan Project Botan The Curve25519 code in botan before 1.11.31, on systems without a native 128-bit integer type, might allow attackers to have unspecified impact via vectors related to undefined behavior, as demonstrated on 32-bit ARM systems compiled by Clang. | 9.8 |
| 2017-04-10 | CVE-2015-7826 | Improper Certificate Validation vulnerability in Botan Project Botan botan 1.11.x before 1.11.22 improperly handles wildcard matching against hostnames, which might allow remote attackers to have unspecified impact via a valid X.509 certificate, as demonstrated by accepting *.example.com as a match for bar.foo.example.com. | 9.8 |
| 2017-04-10 | CVE-2015-7825 | Unspecified vulnerability in Botan Project Botan botan before 1.11.22 improperly validates certificate paths, which allows remote attackers to cause a denial of service (infinite loop and memory consumption) via a certificate with a loop in the certificate chain. | 7.5 |
| 2017-04-10 | CVE-2015-7824 | Information Exposure vulnerability in Botan Project Botan botan 1.11.x before 1.11.22 makes it easier for remote attackers to decrypt TLS ciphertext data via a padding-oracle attack against TLS CBC ciphersuites. | 7.5 |
| 2017-01-30 | CVE-2016-9132 | Integer Overflow or Wraparound vulnerability in Botan Project Botan In Botan 1.8.0 through 1.11.33, when decoding BER data an integer overflow could occur, which would cause an incorrect length field to be computed. | 9.8 |
| 2016-10-28 | CVE-2016-8871 | Information Exposure vulnerability in Botan Project Botan In 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. | 6.2 |
| 2016-05-13 | CVE-2016-2850 | Improper Input Validation vulnerability in multiple products Botan 1.11.x before 1.11.29 does not enforce TLS policy for (1) signature algorithms and (2) ECC curves, which allows remote attackers to conduct downgrade attacks via unspecified vectors. | 7.5 |
| 2016-05-13 | CVE-2016-2849 | Information Exposure vulnerability in multiple products Botan before 1.10.13 and 1.11.x before 1.11.29 do not use a constant-time algorithm to perform a modular inverse on the signature nonce k, which might allow remote attackers to obtain ECDSA secret keys via a timing side-channel attack. | 7.5 |