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 co
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.
- Published
- Jan 30, 2017
- Updated
- Jun 16, 2026
- EPSS
- 2.0% · 80th percentile
- CWE
- CWE-190
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
40
Plan
Add it to your regular patch cycle.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.0%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| botan project | botan | cpe:2.3:a:botan_project:botan |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- botan project botan1.10.0
- botan project botan1.10.1
- botan project botan1.10.10
- botan project botan1.10.11
- botan project botan1.10.12
- botan project botan1.10.13
- botan project botan1.10.14
- botan project botan1.10.15
- botan project botan1.10.2
- botan project botan1.10.3
- botan project botan1.10.4
- botan project botan1.10.5
- botan project botan1.10.6
- botan project botan1.10.7
- botan project botan1.10.8
- botan project botan1.10.9
- botan project botan1.11.0
- botan project botan1.11.1
- botan project botan1.11.10
- botan project botan1.11.11
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:7 | botan1.10 | before 1.10.5-1+deb7u2 | 1.10.5-1+deb7u2 |
| openSUSE:Tumbleweed | Botan | before 2.18.1-1.3 | 2.18.1-1.3 |
| SUSE:Linux Enterprise Software Development Kit 11 SP4 | Botan | before 1.6.5-4.1 | 1.6.5-4.1 |
| SUSE:Linux Enterprise Software Development Kit 11 SP4 | Botan | before 1.6.5-6.1 | 1.6.5-6.1 |
| SUSE:Linux Enterprise Software Development Kit 12 SP1 | Botan | before 1.10.9-3.1 | 1.10.9-3.1 |
Same product
botan project: all recordsOther highest-scoring records for the same primary product.
- CVE-2016-2196Heap-based buffer overflow in the P-521 reduction function in Botan 1.11.x before 1.11.27 allows remote attackers to cause a denial of servi41Plan
- CVE-2016-2195Integer overflow in the PointGFp constructor in Botan before 1.10.11 and 1.11.x before 1.11.27 allows remote attackers to overwrite memory a41Plan
- CVE-2021-24115In Botan before 2.17.3, constant-time computations are not used for certain decoding and encoding operations (base32, base58, base64, and he40Plan
- CVE-2018-9127Botan 2.2.0 - 2.4.0 (fixed in 2.5.0) improperly handled wildcard certificates and could accept certain certificates as valid for hostnames w39Monitor
- CVE-2017-2801A programming error exists in a way Randombit Botan cryptographic library version 2.0.1 implements x500 string comparisons which could lead 39Monitor
- CVE-2016-6878The Curve25519 code in botan before 1.11.31, on systems without a native 128-bit integer type, might allow attackers to have unspecified imp39Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:botan1.10 | 1.10.5-1+deb7u2 · Debian:7 | Package registry (OSV) |
| opensuse:Botan | 2.18.1-1.3 · openSUSE:Tumbleweed | Package registry (OSV) |
| suse:Botan | 1.10.9-3.1 · SUSE:Linux Enterprise Software Development Kit 12 SP1 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-190 · Integer Overflow or WraparoundCVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- www.securityfocus.com/bid/95879
- github.com/randombit/botan/commit/987ad747db6d0d7e36f840398f3cf02e2fbfd90f
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/4OUDGVRQYQUL7F5MRP3LAV7EHRJG4BBE/
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/Z2Y3JLMTE3VIV4X5X6SXVZTJBDDLCS3D/
Vendor advisories and official records. Exploit/PoC links are deliberately left out.