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
References
Link | Resource |
---|---|
https://cryptopp.com | Vendor Advisory |
https://github.com/weidai11/cryptopp/issues/1080 | Exploit Third Party Advisory |
https://github.com/weidai11/cryptopp/issues/1080#issuecomment-996492222 | Exploit Issue Tracking Third Party Advisory |
Configurations
History
07 Nov 2023, 03:39
Type | Values Removed | Values Added |
---|---|---|
Summary | 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 |
Information
Published : 2021-11-04 21:15
Updated : 2024-08-04 04:16
NVD link : CVE-2021-43398
Mitre link : CVE-2021-43398
CVE.ORG link : CVE-2021-43398
JSON object : View
Products Affected
cryptopp
- crypto\+\+
CWE
CWE-203
Observable Discrepancy