Vulnerabilities · 2016 · Bouncycastle
CVE-2016-2427
Bouncycastle Bc-java vulnerability
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 products
Bc-java, Android. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Bouncycastle Bc-java runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
More vulnerabilities in Bouncycastle products
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.