Name | CVE-2016-7420 |
Description | 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. |
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) | bullseye | 8.4.0-1 | vulnerable |
| bookworm | 8.7.0+git220824-1 | vulnerable |
| sid, trixie | 8.9.0-1.1 | vulnerable |
The information below is based on the following data on fixed versions.
Package | Type | Release | Fixed Version | Urgency | Origin | Debian Bugs |
---|
libcrypto++ | source | (unstable) | (unfixed) | unimportant | | |
Notes
https://github.com/weidai11/cryptopp/issues/277
The scope of this CVE is the documentation bug, lacking treatment of
-DNDEBUG and Static Initialization
Documentation added in https://github.com/weidai11/cryptopp/commit/553049ba297d89d9e8fbf2204acb40a8a53f5cd6