CVE-2016-9132

critical
Published 2017-01-30 ยท Modified 2026-05-13
CVSS v3
9.8
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS v4 NEW
โ€”
not yet in upstream
VIR risk
9.8

Description

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.

Predictions

Exploit likelihood
97%
Patch ETA
โ€”

Heuristic predictions, AS-IS, for prioritization only.

Mitigations

No mitigations published for this CVE yet.

The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or โ€” if you've already worked around this in production โ€” publish your fix to the community-verified tier.

โœš Propose a mitigation on Community โ†’ Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here with source_tier=community-verified.

OS impact

suse SUSE Affected 1 release
VersionStatusFixed in
โ€” Affected โ€”

Application impact

VendorProductVersionsFixed
botan_projectbotan1.8.0
botan_projectbotan1.8.1
botan_projectbotan1.8.2
botan_projectbotan1.8.3
botan_projectbotan1.8.4
botan_projectbotan1.8.5
botan_projectbotan1.8.6
botan_projectbotan1.8.7
botan_projectbotan1.8.8
botan_projectbotan1.8.9
botan_projectbotan1.8.10
botan_projectbotan1.8.11
botan_projectbotan1.8.12
botan_projectbotan1.8.13
botan_projectbotan1.8.14
botan_projectbotan1.8.15
botan_projectbotan1.9.0
botan_projectbotan1.9.1
botan_projectbotan1.9.2
botan_projectbotan1.9.3
botan_projectbotan1.9.4
botan_projectbotan1.9.5
botan_projectbotan1.9.6
botan_projectbotan1.9.7
botan_projectbotan1.9.8
botan_projectbotan1.9.9
botan_projectbotan1.9.10
botan_projectbotan1.9.11
botan_projectbotan1.9.12
botan_projectbotan1.9.13
botan_projectbotan1.9.14
botan_projectbotan1.9.15
botan_projectbotan1.9.16
botan_projectbotan1.9.17
botan_projectbotan1.9.18
botan_projectbotan1.10.0
botan_projectbotan1.10.1
botan_projectbotan1.10.2
botan_projectbotan1.10.3
botan_projectbotan1.10.4
botan_projectbotan1.10.5
botan_projectbotan1.10.6
botan_projectbotan1.10.7
botan_projectbotan1.10.8
botan_projectbotan1.10.9
botan_projectbotan1.10.10
botan_projectbotan1.10.11
botan_projectbotan1.10.12
botan_projectbotan1.10.13
botan_projectbotan1.10.14
botan_projectbotan1.10.15
botan_projectbotan1.11.0
botan_projectbotan1.11.1
botan_projectbotan1.11.2
botan_projectbotan1.11.3
botan_projectbotan1.11.4
botan_projectbotan1.11.5
botan_projectbotan1.11.6
botan_projectbotan1.11.7
botan_projectbotan1.11.8
botan_projectbotan1.11.9
botan_projectbotan1.11.10
botan_projectbotan1.11.11
botan_projectbotan1.11.12
botan_projectbotan1.11.13
botan_projectbotan1.11.14
botan_projectbotan1.11.15
botan_projectbotan1.11.16
botan_projectbotan1.11.17
botan_projectbotan1.11.18
botan_projectbotan1.11.19
botan_projectbotan1.11.20
botan_projectbotan1.11.21
botan_projectbotan1.11.23
botan_projectbotan1.11.24
botan_projectbotan1.11.25
botan_projectbotan1.11.26
botan_projectbotan1.11.27
botan_projectbotan1.11.28
botan_projectbotan1.11.29
botan_projectbotan1.11.30
botan_projectbotan1.11.31
botan_projectbotan1.11.32
botan_projectbotan1.11.33

References

CWEs

CWE-190

Community-verified mitigations for this CVE will appear above when contributors publish them.

Verify integrity in audit chain (admin only). AS-IS.