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.
{
"binaries": [
{
"binary_version": "5.6.1-6+deb8u3ubuntu0.1~esm1",
"binary_name": "libcrypto++-dev"
},
{
"binary_version": "5.6.1-6+deb8u3ubuntu0.1~esm1",
"binary_name": "libcrypto++-utils"
},
{
"binary_version": "5.6.1-6+deb8u3ubuntu0.1~esm1",
"binary_name": "libcrypto++9"
}
]
}