Crypto Cryptopp Crypto

Do you want an email whenever new security vulnerabilities are reported in Cryptopp Crypto?

By the Year

In 2024 there have been 0 vulnerabilities in Cryptopp Crypto . Last year Crypto had 4 security vulnerabilities published. Right now, Crypto is on track to have less security vulnerabilities in 2024 than it did last year.

Year Vulnerabilities Average Score
2024 0 0.00
2023 4 7.10
2022 0 0.00
2021 2 5.60
2020 0 0.00
2019 1 5.90
2018 0 0.00

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

ModularSquareRoot in Crypto++ (aka cryptopp) through 8.9.0

CVE-2023-50981 7.5 - High - December 18, 2023

ModularSquareRoot in Crypto++ (aka cryptopp) through 8.9.0 allows attackers to cause a denial of service (infinite loop) via crafted DER public-key data associated with squared odd numbers, such as the square of 268995137513890432434389773128616504853.

Infinite Loop

gf2n.cpp in Crypto++ (aka cryptopp) through 8.9.0

CVE-2023-50980 7.5 - High - December 18, 2023

gf2n.cpp in Crypto++ (aka cryptopp) through 8.9.0 allows attackers to cause a denial of service (application crash) via DER public-key data for an F(2^m) curve, if the degree of each term in the polynomial is not strictly decreasing.

Crypto++ (aka cryptopp) through 8.9.0 has a Marvin side channel during decryption with PKCS#1 v1.5 padding.

CVE-2023-50979 5.9 - Medium - December 18, 2023

Crypto++ (aka cryptopp) through 8.9.0 has a Marvin side channel during decryption with PKCS#1 v1.5 padding.

Side Channel Attack

Crypto++ through 8.4 contains a timing side channel in ECDSA signature generation

CVE-2022-48570 7.5 - High - August 22, 2023

Crypto++ through 8.4 contains a timing side channel in ECDSA signature generation. Function FixedSizeAllocatorWithCleanup could write to memory outside of the allocation if the allocated memory was not 16-byte aligned. NOTE: this issue exists because the CVE-2019-14318 fix was intentionally removed for functionality reasons.

Memory Corruption

Crypto++ (aka Cryptopp) 8.6.0 and earlier contains a timing leakage in MakePublicKey()

CVE-2021-43398 5.3 - Medium - November 04, 2021

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

CVE-2021-40530 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

CVE-2019-14318 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

Crypto++ (aka cryptopp) through 5.6.4 does not document the requirement for a compile-time NDEBUG definition disabling the many assert calls

CVE-2016-7420 5.9 - Medium - September 16, 2016

Crypto++ (aka cryptopp) through 5.6.4 does not document the requirement for a compile-time NDEBUG definition disabling the many assert calls that are unintended in production use, which might allow context-dependent attackers to obtain sensitive information by leveraging access to process memory after an assertion failure, as demonstrated by reading a core dump.

Information Disclosure

Stay on top of Security Vulnerabilities

Want an email whenever new vulnerabilities are published for Cryptopp Crypto or by Cryptopp? Click the Watch button to subscribe.

Cryptopp
Vendor

subscribe