CVE-2016-3995: Infoleak

Published Feb 13, 2017
·
Updated

The timing attack protection in Rijndael::Enc::ProcessAndXorBlock and Rijndael::Dec::ProcessAndXorBlock in Crypto++ (aka cryptopp) before 5.6.4 may be optimized out by the compiler, which allows attackers to conduct timing attacks.

Affected Software

1 affected component
Cryptopp Crypto\+\+<=5.6.3

Event History

Feb 13, 2017
CVE Published
via MITRE·06:00 PM
Data Sourced
via MITRE·06:00 PM
Description
Data Sourced
via NVD·06:59 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2016-3995?

CVE-2016-3995 is considered a high-severity vulnerability due to its potential to allow timing attacks.

2

How do I fix CVE-2016-3995?

To fix CVE-2016-3995, upgrade Crypto++ to version 5.6.4 or later.

3

What does CVE-2016-3995 affect?

CVE-2016-3995 affects Crypto++ versions up to and including 5.6.3.

4

What type of attack is enabled by CVE-2016-3995?

CVE-2016-3995 allows attackers to conduct timing attacks due to optimized-out timing protection.

5

Who is vulnerable to CVE-2016-3995?

Developers and users of affected versions of Crypto++ are vulnerable to CVE-2016-3995.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203