| Name | CVE-2021-43398 |
| Description | Crypto++ (aka Cryptopp) 8.6.0 and earlier contains a timing leakage in MakePublicKey(). There is a clear correlation between execution time and private key length, which may cause disclosure of the length information of the private key. This might allow attackers to conduct timing attacks. NOTE: this report is disputed by the vendor and multiple third parties. The execution-time differences are intentional. A user may make a choice of a longer key as a tradeoff between strength and performance. In making this choice, the amount of information leaked to an adversary is of infinitesimal value |
| Source | CVE (at NVD; CERT, LWN, oss-sec, fulldisc, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more) |
Vulnerable and fixed packages
The table below lists information on source packages.
| Source Package | Release | Version | Status |
|---|
| libcrypto++ (PTS) | jessie, jessie (lts) | 5.6.1-6+deb8u3 | vulnerable |
The information below is based on the following data on fixed versions.
| Package | Type | Release | Fixed Version | Urgency | Origin | Debian Bugs |
|---|
| libcrypto++ | source | jessie | (unfixed) | end-of-life | | |
Notes
Disputed Crypto++ issue, also see #1000227
https://github.com/weidai11/cryptopp/issues/1080
As per upstream believed to be the expected behaviour:
https://github.com/weidai11/cryptopp/issues/1080#issuecomment-996492222