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.
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
| Link | Tags |
|---|---|
| https://github.com/weidai11/cryptopp/commit/553049ba297d89d9e8fbf2204acb40a8a53f5cd6 | issue tracking third party advisory patch |
| http://www.securityfocus.com/bid/92988 | vdb entry |
| http://www.openwall.com/lists/oss-security/2016/09/16/1 | third party advisory mailing list |
| https://github.com/weidai11/cryptopp/issues/277 | issue tracking third party advisory patch |
| http://www.openwall.com/lists/oss-security/2016/09/15/12 | third party advisory mailing list |
| http://www.openwall.com/lists/oss-security/2023/09/28/2 | mailing list |
| http://www.openwall.com/lists/oss-security/2023/09/28/4 | mailing list |