Show filters
26 Total Results
Displaying 11-20 of 26
Sort by:
Attacker Value
Unknown

CVE-2016-6879

Disclosure Date: April 10, 2017 (last updated November 26, 2024)
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.
0
Attacker Value
Unknown

CVE-2015-7824

Disclosure Date: April 10, 2017 (last updated November 26, 2024)
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.
0
Attacker Value
Unknown

CVE-2015-7826

Disclosure Date: April 10, 2017 (last updated November 26, 2024)
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.
0
Attacker Value
Unknown

CVE-2015-7825

Disclosure Date: April 10, 2017 (last updated November 26, 2024)
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.
0
Attacker Value
Unknown

CVE-2016-6878

Disclosure Date: April 10, 2017 (last updated November 26, 2024)
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.
0
Attacker Value
Unknown

CVE-2016-9132

Disclosure Date: January 30, 2017 (last updated November 08, 2023)
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. Some API callers may use the returned (incorrect and attacker controlled) length field in a way which later causes memory corruption or other failure.
0
Attacker Value
Unknown

CVE-2016-8871

Disclosure Date: October 28, 2016 (last updated November 25, 2024)
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.
0
Attacker Value
Unknown

CVE-2016-2850

Disclosure Date: May 13, 2016 (last updated November 25, 2024)
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.
0
Attacker Value
Unknown

CVE-2015-7827

Disclosure Date: May 13, 2016 (last updated November 25, 2024)
Botan before 1.10.13 and 1.11.x before 1.11.22 make it easier for remote attackers to conduct million-message attacks by measuring time differences, related to decoding of PKCS#1 padding.
0
Attacker Value
Unknown

CVE-2015-5727

Disclosure Date: May 13, 2016 (last updated November 25, 2024)
The BER decoder in Botan 1.10.x before 1.10.10 and 1.11.x before 1.11.19 allows remote attackers to cause a denial of service (memory consumption) via unspecified vectors, related to a length field.
0