CVE-2016-2427: Infoleak
DISPUTED The AES-GCM specification in RFC 5084, as used in Android 5.x and 6.x, recommends 12 octets for the aes-ICVlen parameter field, which might make it easier for attackers to defeat a cryptographic protection mechanism and discover an authentication key via a crafted application, aka internal bug 26234568. NOTE: The vendor disputes the existence of this potential issue in Android, stating "This CVE was raised in error: it referred to the authentication tag size in GCM, whose default according to ASN.1 encoding (12 bytes) can lead to vulnerabilities. After careful consideration, it was decided that the insecure default value of 12 bytes was a default only for the encoding and not default anywhere else in Android, and hence no vulnerability existed."
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2016-2427?
CVE-2016-2427 is classified as a moderate severity vulnerability due to its potential impact on cryptographic protections.
How do I fix CVE-2016-2427?
To mitigate CVE-2016-2427, update the affected Android versions to the latest security patches released by Google.
What software is affected by CVE-2016-2427?
CVE-2016-2427 affects Android versions 5.x and 6.x, particularly applications using the Bouncy Castle crypto API.
What is the impact of CVE-2016-2427?
The vulnerability may allow attackers to exploit weaknesses in the AES-GCM implementation to uncover authentication keys.
Is CVE-2016-2427 limited to specific devices?
Yes, CVE-2016-2427 specifically affects devices running Android 5.0 to 6.0.1 with software vulnerabilities in the cryptographic API.