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.
References
Link | Resource |
---|---|
http://www.openwall.com/lists/oss-security/2016/09/15/12 | Mailing List Third Party Advisory |
http://www.openwall.com/lists/oss-security/2016/09/16/1 | Mailing List Third Party Advisory |
http://www.openwall.com/lists/oss-security/2023/09/28/2 | |
http://www.openwall.com/lists/oss-security/2023/09/28/4 | |
http://www.securityfocus.com/bid/92988 | |
https://github.com/weidai11/cryptopp/commit/553049ba297d89d9e8fbf2204acb40a8a53f5cd6 | Issue Tracking Patch Third Party Advisory |
https://github.com/weidai11/cryptopp/issues/277 | Issue Tracking Patch Third Party Advisory |
Configurations
History
No history.
Information
Published : 2016-09-16 05:59
Updated : 2024-02-04 18:53
NVD link : CVE-2016-7420
Mitre link : CVE-2016-7420
CVE.ORG link : CVE-2016-7420
JSON object : View
Products Affected
cryptopp
- crypto\+\+
CWE
CWE-200
Exposure of Sensitive Information to an Unauthorized Actor