CVE-2017-14737: A cryptographic cache-based side channel in the RSA implementation in Botan before 1.10.17, and 1.11.x and 2.x before 2.3.0, allows a local…
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.31% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: botan1.10 (Debian:7) 1.10.5-1+deb7u4; botan1.10 (Debian:9) 1.10.17-1+deb9u1; Botan (openSUSE:Tumbleweed) 2.18.1-1.3.
Low priority for now. Upgrade to botan1.10 (Debian:7) 1.10.5-1+deb7u4; botan1.10 (Debian:9) 1.10.17-1+deb9u1; Botan (openSUSE:Tumbleweed) 2.18.1-1.3 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
A cryptographic cache-based side channel in the RSA implementation in Botan before 1.10.17, and 1.11.x and 2.x before 2.3.0, allows a local attacker to recover information about RSA secret keys, as demonstrated by CacheD. This occurs because an array is indexed with bits derived from a secret key.
- Published
- Sep 25, 2017
- Updated
- Jun 16, 2026
- EPSS
- 0.3% · 25th percentile
- CWE
- —
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| botan project | botan | cpe:2.3:a:botan_project:botan |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- botan project botanup to 1.10.16 inclusive
- botan project botan1.11.0
- botan project botan1.11.1
- botan project botan1.11.10
- botan project botan1.11.11
- botan project botan1.11.12
- botan project botan1.11.13
- botan project botan1.11.14
+12 more rows
- botan project botan1.11.15
- botan project botan1.11.16
- botan project botan1.11.17
- botan project botan1.11.18
- botan project botan1.11.19
- botan project botan1.11.2
- botan project botan1.11.20
- botan project botan1.11.21
- botan project botan1.11.22
- botan project botan1.11.23
- botan project botan1.11.24
- botan project botan1.11.25
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+deb7u4 | 1.10.5-1+deb7u4 |
| Debian:9 | botan1.10 | before 1.10.17-1+deb9u1 | 1.10.17-1+deb9u1 |
| openSUSE:Tumbleweed | Botan | before 2.18.1-1.3 | 2.18.1-1.3 |
| SUSE:Linux Enterprise Software Development Kit 12 SP2 | Botan | before 1.10.9-4.3.1 | 1.10.9-4.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…41Plan
- 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…41Plan
- CVE-2021-24115In Botan before 2.17.3, constant-time computations are not used for certain decoding and encoding operations (base32, base58, base64, and…40Plan
Published before and after this one in the same product
- ← EarlierCVE-2016-6879Apr 10, 2017 · The X509_Certificate::allowed_usage function in botan 1.11.x before 1.11.31 might allow attackers to have unspecified impact by leveraging…30Monitor
- ← EarlierCVE-2017-2801May 24, 2017 · A programming error exists in a way Randombit Botan cryptographic library version 2.0.1 implements x500 string comparisons which could lead…39Monitor
- Later →CVE-2018-9127Apr 2, 2018 · Botan 2.2.0 - 2.4.0 (fixed in 2.5.0) improperly handled wildcard certificates and could accept certain certificates as valid for hostnames…39Monitor
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+deb7u4 · Debian:7 | Package registry (OSV) |
| opensuse:Botan | 2.18.1-1.3 · openSUSE:Tumbleweed | Package registry (OSV) |
| suse:Botan | 1.10.9-4.3.1 · SUSE:Linux Enterprise Software Development Kit 12 SP2 | 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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.