By the Year
In 2022 there have been 0 vulnerabilities in Cryptopp Crypto . Last year Crypto had 2 security vulnerabilities published. Right now, Crypto is on track to have less security vulnerabilities in 2022 than it did last year.
It may take a day or so for new Crypto vulnerabilities to show up in the stats or in the list of recent security vulnerabilties. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Cryptopp Crypto Security Vulnerabilities
** DISPUTED ** Crypto++ (aka Cryptopp) 8.6.0 and earlier contains a timing leakage in MakePublicKey()
5.3 - Medium
- November 04, 2021
** DISPUTED ** 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.
Side Channel Attack
The ElGamal implementation in Crypto++ through 8.5
5.9 - Medium
- September 06, 2021
The ElGamal implementation in Crypto++ through 8.5 allows plaintext recovery because, during interaction between two cryptographic libraries, a certain dangerous combination of the prime defined by the receiver's public key, the generator defined by the receiver's public key, and the sender's ephemeral exponents can lead to a cross-configuration attack against OpenPGP.
Use of a Broken or Risky Cryptographic Algorithm
Crypto++ 8.3.0 and earlier contains a timing side channel in ECDSA signature generation
5.9 - Medium
- July 30, 2019
Crypto++ 8.3.0 and earlier contains a timing side channel in ECDSA signature generation. This allows a local or remote attacker, able to measure the duration of hundreds to thousands of signing operations, to compute the private key used. The issue occurs because scalar multiplication in ecp.cpp (prime field curves, small leakage) and algebra.cpp (binary field curves, large leakage) is not constant time and leaks the bit length of the scalar among other information.
Communication Channel Errors