CVE-2016-2427
Android AES-GCM Authentication Tag Size Vulnerability
Description
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.
INFO
Published Date :
April 18, 2016, 12:59 a.m.
Last Modified :
Nov. 21, 2024, 2:48 a.m.
Source :
[email protected]
Remotely Exploitable :
No
Impact Score :
3.6
Exploitability Score :
1.8
Affected Products
The following products are affected by CVE-2016-2427
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2016-2427.
| URL | Resource |
|---|---|
| http://source.android.com/security/bulletin/2016-04-02.html | Vendor Advisory |
| http://source.android.com/security/bulletin/2016-04-02.html | Vendor Advisory |
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2016-2427 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2016-2427 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by [email protected]
Aug. 06, 2024
Action Type Old Value New Value -
CVE Modified by [email protected]
May. 17, 2024
Action Type Old Value New Value -
CVE Modified by [email protected]
May. 14, 2024
Action Type Old Value New Value -
CVE Modified by [email protected]
Apr. 11, 2024
Action Type Old Value New Value -
CVE Modified by [email protected]
Mar. 21, 2024
Action Type Old Value New Value Added Tag Android (associated with Google Inc. or Open Handset Alliance) disputed -
CVE Modified by [email protected]
Nov. 07, 2023
Action Type Old Value New Value Changed Description ** 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." 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. -
CVE Translated by [email protected]
Aug. 09, 2016
Action Type Old Value New Value Removed Translation asn1/cms/GCMParameters.java en las APIs Bouncy Castle Crypto 1.54 para Java, como se utiliza en Android 5.0.x en versiones anteriores a 5.0.2, 5.1.x en versiones anteriores a 5.1.1 y 6.x en versiones anteriores a 2016-04-01, tiene un valor AES-GCM-ICVlen indebido, lo que hace más fácil para atacantes vencer un mecanismo de protección criptográfico y descubrir una clave de autenticación a través de una aplicación manipulada, también conocida como error interno 26234568. Added Translation **DISPUTADA** La especificación AES-GCM en RFC 5084,como es utilizado en Android 5.x y 6.x, recomienda 12 octetos para el campo de parámetro aes-ICVlen, lo que podría facilitar a atacantes derrotar el mecanismo de protección criptográfico y descubrir una clave de autenticación a través de una aplicación manipulada, también conocido como error interno 26234568. NOTA: El vendedor disputa la existencia de este potencial problema en Android, indicando que "Esta CVE fue levantada por error: se refería al tamaño de la etiqueta de autenticación en GCM, cuyo defecto de acuerdo con la codificación ASN.1 (12 bytes) puede llevar a vulnerabilidades. Después de una cuidadosa consideración, se decidió que el valor del defecto de seguridad de 12 bytes era sólo un fallo para la codificación y no por defecto en cualquier otro lugar en Android, y por lo tanto no existía vulnerabilidad." -
CVE Modified by [email protected]
Aug. 09, 2016
Action Type Old Value New Value Changed Description asn1/cms/GCMParameters.java in the Bouncy Castle Crypto APIs 1.54 for Java, as used in Android 5.0.x before 5.0.2, 5.1.x before 5.1.1, and 6.x before 2016-04-01, has an improper AES-GCM-ICVlen value, which makes it easier for attackers to defeat a cryptographic protection mechanism and discover an authentication key via a crafted application, aka internal bug 26234568. ** 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." Removed Reference https://android.googlesource.com/platform/libcore/+/efd369d996fd38c50a50ea0de8f20507253cb6de Removed Reference https://android.googlesource.com/platform/external/bouncycastle/+/b3bddea0f33c0459293c6419569ad151b4a7b44b -
Modified Analysis by [email protected]
Apr. 26, 2016
Action Type Old Value New Value Changed CPE Configuration Configuration 1 OR *cpe:2.3:o:google:android:6.0.1:*:*:*:*:*:*:* *cpe:2.3:o:google:android:6.0:*:*:*:*:*:*:* *cpe:2.3:o:google:android:5.1.0:*:*:*:*:*:*:* *cpe:2.3:o:google:android:5.1:*:*:*:*:*:*:* *cpe:2.3:o:google:android:5.0.1:*:*:*:*:*:*:* *cpe:2.3:o:google:android:5.0:*:*:*:*:*:*:* Configuration 2 OR *cpe:2.3:a:bouncy_castle:legion-of-the-bouncy-castle-java-crytography-api:1.54:*:*:*:*:*:*:* Configuration 1 OR *cpe:2.3:a:bouncycastle:legion-of-the-bouncy-castle-java-crytography-api:1.54:*:*:*:*:*:*:* Configuration 2 OR *cpe:2.3:o:google:android:6.0.1:*:*:*:*:*:*:* *cpe:2.3:o:google:android:6.0:*:*:*:*:*:*:* *cpe:2.3:o:google:android:5.1.0:*:*:*:*:*:*:* *cpe:2.3:o:google:android:5.1:*:*:*:*:*:*:* *cpe:2.3:o:google:android:5.0.1:*:*:*:*:*:*:* *cpe:2.3:o:google:android:5.0:*:*:*:*:*:*:* -
Modified Analysis by [email protected]
Apr. 25, 2016
Action Type Old Value New Value Changed CPE Configuration Configuration 1 OR *cpe:2.3:o:google:android:6.0.1:*:*:*:*:*:*:* *cpe:2.3:o:google:android:6.0:*:*:*:*:*:*:* *cpe:2.3:o:google:android:5.1.0:*:*:*:*:*:*:* *cpe:2.3:o:google:android:5.1:*:*:*:*:*:*:* *cpe:2.3:o:google:android:5.0.1:*:*:*:*:*:*:* *cpe:2.3:o:google:android:5.0:*:*:*:*:*:*:* Configuration 2 OR *cpe:2.3:a:bouncy_castle:bouncy_castle:1.54:*:*:*:*:*:*:* Configuration 1 OR *cpe:2.3:o:google:android:6.0.1:*:*:*:*:*:*:* *cpe:2.3:o:google:android:6.0:*:*:*:*:*:*:* *cpe:2.3:o:google:android:5.1.0:*:*:*:*:*:*:* *cpe:2.3:o:google:android:5.1:*:*:*:*:*:*:* *cpe:2.3:o:google:android:5.0.1:*:*:*:*:*:*:* *cpe:2.3:o:google:android:5.0:*:*:*:*:*:*:* Configuration 2 OR *cpe:2.3:a:bouncy_castle:legion-of-the-bouncy-castle-java-crytography-api:1.54:*:*:*:*:*:*:* -
Modified Analysis by [email protected]
Apr. 25, 2016
Action Type Old Value New Value Added CPE Configuration Configuration 1 OR *cpe:2.3:o:google:android:6.0.1:*:*:*:*:*:*:* *cpe:2.3:o:google:android:6.0:*:*:*:*:*:*:* *cpe:2.3:o:google:android:5.1.0:*:*:*:*:*:*:* *cpe:2.3:o:google:android:5.1:*:*:*:*:*:*:* *cpe:2.3:o:google:android:5.0.1:*:*:*:*:*:*:* *cpe:2.3:o:google:android:5.0:*:*:*:*:*:*:* Configuration 2 OR *cpe:2.3:a:bouncy_castle:bouncy_castle:1.54:*:*:*:*:*:*:* Added CVSS V2 (AV:N/AC:M/Au:N/C:P/I:N/A:N) Added CVSS V3 AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N Changed Reference Type http://source.android.com/security/bulletin/2016-04-02.html No Types Assigned http://source.android.com/security/bulletin/2016-04-02.html Advisory Added CWE CWE-200 -
Initial Analysis by [email protected]
Apr. 20, 2016
Action Type Old Value New Value -
Initial Analysis by [email protected]
Apr. 20, 2016
Action Type Old Value New Value
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2016-2427 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2016-2427
weaknesses.
Exploit Prediction
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days.
0.06 }} 0.00%
score
0.21629
percentile