Skip to content
Fencer Intel
medium 5.5

CVE-2017-14737 json

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…

published 2017-09-26 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-6233

cvss
5.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 24%
public exploits
0
none known

Summary

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.

Patch / fix

  • botan1.10 Ubuntu Pro 14.04 LTS 1.10.5-1+deb7u1ubuntu0.14.04.1+esm1

ubuntu advisories UBUNTU-CVE-2017-14737

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • Botan SLE Software Development Kit 12 SP3, SLE Software Development Kit 12 SP2 1.10.9-4.3.1

suse advisories SUSE-SU-2017:2855-1

  • Botan openSUSE Tumbleweed 2.18.1-1.3

opensuse advisories openSUSE-SU-2024:10594-1

  • botan Arch Linux 2.3.0-1

arch linux advisories AVG-416

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2017-14737 updated cvss 5.5

botan: cryptographic cache-based side channel in the RSA implementation

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.32% chance of exploitation in the next 30 days, higher than 24% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 2.1 AV:L/AC:L/Au:N/C:P/I:N/A:N

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.