Every CVE Search/ Get API key

CVE-2016-9132

In Botan 1.8.0 through 1.11.33, when decoding BER data an integer overflow could occur, which...

9.8 CriticalFix available

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.

Attack profile

How easy it is to exploit

Attack vector
Network
Complexity
Low
Privileges needed
None
User interaction
None

What an attacker can affect

Confidentiality
High
Integrity
High
Availability
High

Exploit likelihood

2.95%Up 1.9 points since Feb 4, 2022
90%50%10%1%

What each source reports

NVD Score used 9.8

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.

Record
CVE-2016-9132
CVSS 3.0
9.8 CriticalCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS 2.0
7.5 HighAV:N/AC:L/Au:N/C:P/I:P/A:P
Weakness
CWE-190
Updated
2026-11-02
CVE List No score

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.

Record
CVE-2016-9132
Updated
2026-11-02
EUVDEUVD-2016-9949 No score

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.

Record
EUVD-2016-9949
Updated
2026-11-03
GitHub AdvisoriesGHSA-674g-g96j-pr63 9.8

In Botan 1.8.0 through 1.11.33, when decoding BER data an integer overflow could occur, which...

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.

Record
GHSA-674g-g96j-pr63
CVSS 3.0
9.8 CriticalCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness
CWE-190
Updated
2026-11-02
OSV 9.8

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.

Record
CVE-2016-9132
CVSS 3.0
9.8 CriticalCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Updated
2026-11-02
OSVUBUNTU-CVE-2016-9132 9.8

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.

Record
UBUNTU-CVE-2016-9132
CVSS 3.0
9.8 CriticalCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Updated
2026-11-02
Show 5 moreShow less
OSVMGASA-2017-0321 No score

Updated botan packages fix security vulnerabilities

While decoding BER length fields, an integer overflow could occur. This could occur while parsing untrusted inputs such as X.509 certificates. The overflow does not seem to lead to any obviously exploitable condition, but exploitation cannot be positively ruled out. Only 32-bit platforms are likely affected; to cause an overflow on 64-bit the parsed data would have to be many gigabytes (CVE-2016-9132).

Aleksandar Nikolic discovered that an error in the x509 parser of the Botan crypto library could result in an out-of-bounds memory read, resulting in denial of service or an information leak if processing a malformed certificate (CVE-2017-2801).

Record
MGASA-2017-0321
Updated
2026-11-02
OSVopenSUSE-SU-2024:10594-1 No score

Botan-2.18.1-1.3 on GA media

These are all security issues fixed in the Botan-2.18.1-1.3 package on the GA media of openSUSE Tumbleweed.

Record
openSUSE-SU-2024:10594-1
Updated
2026-11-02
OSVSUSE-SU-2017:1222-1 No score

Security update for Botan

This update for Botan to version 1.10.9 fixes the following issues:

These security issues were fixed:

  • CVE-2015-5726: The BER decoder in Botan 0.10.x allowed remote attackers to cause a denial of service (application crash) via an empty BIT STRING in ASN.1 data (bsc#968025).
  • CVE-2015-5727: The BER decoder in Botan 1.10.x allowed remote attackers to cause a denial of service (memory consumption) via unspecified vectors, related to a length field (bsc#968026).
  • CVE-2015-7827: Botan make it easier for remote attackers to conduct million-message attacks by measuring time differences, related to decoding of PKCS#1 padding (bsc#968030).
  • CVE-2016-2849: Botan do not use a constant-time algorithm to perform a modular inverse on the signature nonce k, which might allowed remote attackers to obtain ECDSA secret keys via a timing side-channel attack (bsc#977420).
  • CVE-2016-9132: In Botan 1.8.0 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 caused memory corruption or other failure (bsc#1013209).
  • CVE-2016-2194: The ressol function in Botan allowed remote attackers to cause a denial of service (infinite loop) via unspecified input to the OS2ECP function, related to a composite modulus (bsc#965621).
  • CVE-2016-2195: Integer overflow in the PointGFp constructor in Botan allowed remote attackers to overwrite memory and possibly execute arbitrary code via a crafted ECC point, which triggers a heap-based buffer overflow (bsc#965620).
  • CVE-2017-2801: Incorrect comparison in X.509 DN strings (bsc#1033605).
  • CVE-2014-9742: The Miller-Rabin primality check in Botan improperly used a single random base, which made it easier for remote attackers to defeat cryptographic protection mechanisms via a DH group (bsc#974521).

These non-security issues were fixed:

  • Fixed EAX tag verification to run in constant time
  • The default TLS policy now disables SSLv3.
  • A crash could have occured when reading from a blocking random device if the device initially indicated that entropy was available but a concurrent process drained the entropy pool before the read was initiated.
  • Fixed decoding indefinite length BER constructs that contain a context sensitive tag of zero.
  • The key length limit on HMAC has been raised to 512 bytes, allowing the use of very long passphrases with PBKDF2.
  • OAEP had two bugs, one of which allowed it to be used even if the key was too small, and the other of which would cause a crash during decryption if the EME data was too large for the associated key.
Record
SUSE-SU-2017:1222-1
Updated
2026-11-02
OSVSUSE-SU-2017:1305-1 No score

Security update for Botan

This update for Botan fixes the following issues:

  • CVE-2015-7827: PKCS #1 v1.5 decoding was not constant time, it could be used to mount a Bleichenbacher million-message attack (bsc#968030)

  • CVE-2016-9132: While decoding BER length fields, an integer overflow could occur leading to a denial-of-service (bsc#1013209)

Record
SUSE-SU-2017:1305-1
Updated
2026-11-02
OSVSUSE-SU-2017:1351-1 No score

Security update for Botan

This update for Botan fixes the following issues:

  • CVE-2015-7827: PKCS #1 v1.5 decoding was not constant time, it could be used to mount a Bleichenbacher million-message attack (bsc#968030)

  • CVE-2016-9132: While decoding BER length fields, an integer overflow could occur leading to a denial-of-service (bsc#1013209)

Record
SUSE-SU-2017:1351-1
Updated
2026-11-02

Affected products

Affected packages

Affected packages
PackageAffectedFixed
botan1.10
Debian:7
before 1.10.5-1+deb7u2, plus listed versions
1.10.5-11.10.5-1+deb7u1
1.10.5-1+deb7u2
botan
Mageia:5
before 1.10.14-1.mga5
1.10.14-1.mga5
Botan
SUSE:Linux Enterprise Software Development Kit 12 SP1
before 1.10.9-3.1
1.10.9-3.1
Botan
SUSE:Linux Enterprise Software Development Kit 12 SP2
before 1.10.9-3.1
1.10.9-3.1
Botan
SUSE:Linux Enterprise Software Development Kit 11 SP4
before 1.6.5-4.1
1.6.5-4.1
Botan
SUSE:Linux Enterprise Software Development Kit 11 SP4
before 1.6.5-6.1
1.6.5-6.1
botan1.10
Ubuntu:Pro:14.04:LTS
before 1.10.5-1+deb7u1ubuntu0.14.04.1+esm1, plus listed versions
1.10.5-11.10.5-1ubuntu11.10.5-1+deb7u1ubuntu0.14.04.1
1.10.5-1+deb7u1ubuntu0.14.04.1+esm1
botan1.10
Ubuntu:16.04:LTS
All versions, plus listed versions
1.10.10-61.10.12-1
None known
Botan
openSUSE:Tumbleweed
before 2.18.1-1.3
2.18.1-1.3

History

History
RecordedChangedSources
aliasesEUVD
first indexedCVE List, GitHub Advisories, NVD, OSV

Dates are when Every CVE recorded each change. Upstream dates may differ.

In short

CVE-2016-9132 is a critical vulnerability (CVSS 9.8) in Botan Project Botan, published January 16, 2017. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 2.95%, the 87th percentile. Fixed in botan1.10 1.10.5-1+deb7u2.

References

Show 35 moreShow less
MoveEnter Open