// For flags

CVE-2021-29542

Heap buffer overflow in `StringNGrams`

Severity Score

5.5
*CVSS v3.1

Exploit Likelihood

*EPSS

Affected Versions

*CPE

Public Exploits

1
*Multiple Sources

Exploited in Wild

-
*KEV

Decision

-
*SSVC
Descriptions

TensorFlow is an end-to-end open source platform for machine learning. An attacker can cause a heap buffer overflow by passing crafted inputs to `tf.raw_ops.StringNGrams`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/1cdd4da14282210cc759e468d9781741ac7d01bf/tensorflow/core/kernels/string_ngrams_op.cc#L171-L185) fails to consider corner cases where input would be split in such a way that the generated tokens should only contain padding elements. If input is such that `num_tokens` is 0, then, for `data_start_index=0` (when left padding is present), the marked line would result in reading `data[-1]`. The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.

TensorFlow es una plataforma de código abierto de extremo a extremo para el aprendizaje automático. Un atacante puede causar un desbordamiento del búfer al pasar entradas diseñadas a "tf.raw_ops.StringNGrams". Esto es debido a que la implementación (https://github.com/tensorflow/tensorflow/blob/1cdd4da14282210cc759e468d9781741ac7d01bf/tensorflow/core/kernels/string_ngrams_op.cc#L171-L185) no considera los casos de esquina donde la entrada se dividiría de tal manera que los tokens generados solo deben contener elementos de relleno. Si la entrada es tal que "num_tokens" es 0, entonces, para "data_start_index=0" (cuando el relleno a la izquierda está presente), la línea marcada daría como resultado la lectura de "data [-1]". La corrección será incluida en TensorFlow versión 2.5.0. También seleccionaremos este commit en TensorFlow versión 2.4.2, TensorFlow versión 2.3.3, TensorFlow versión 2.2.3 y TensorFlow versión 2.1.4, ya que estos también están afectados y aún están en el rango compatible

*Credits: N/A
CVSS Scores
Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High
Attack Vector
Local
Attack Complexity
High
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low
Attack Vector
Local
Attack Complexity
Low
Authentication
None
Confidentiality
None
Integrity
None
Availability
Partial
* Common Vulnerability Scoring System
SSVC
  • Decision:-
Exploitation
-
Automatable
-
Tech. Impact
-
* Organization's Worst-case Scenario
Timeline
  • 2021-03-30 CVE Reserved
  • 2021-05-14 CVE Published
  • 2023-03-08 EPSS Updated
  • 2024-08-03 CVE Updated
  • 2024-08-03 First Exploit
  • ---------- Exploited in Wild
  • ---------- KEV Due Date
CWE
  • CWE-131: Incorrect Calculation of Buffer Size
  • CWE-787: Out-of-bounds Write
CAPEC
Affected Vendors, Products, and Versions
Vendor Product Version Other Status
Vendor Product Version Other Status <-- --> Vendor Product Version Other Status
Google
Search vendor "Google"
 Tensorflow
Search vendor "Google" for product "Tensorflow"
 < 2.1.4
Search vendor "Google" for product "Tensorflow" and version " < 2.1.4"
-
Affected
Google
Search vendor "Google"
 Tensorflow
Search vendor "Google" for product "Tensorflow"
 >= 2.2.0 < 2.2.3
Search vendor "Google" for product "Tensorflow" and version " >= 2.2.0 < 2.2.3"
-
Affected
Google
Search vendor "Google"
 Tensorflow
Search vendor "Google" for product "Tensorflow"
 >= 2.3.0 < 2.3.3
Search vendor "Google" for product "Tensorflow" and version " >= 2.3.0 < 2.3.3"
-
Affected
Google
Search vendor "Google"
 Tensorflow
Search vendor "Google" for product "Tensorflow"
 >= 2.4.0 < 2.4.2
Search vendor "Google" for product "Tensorflow" and version " >= 2.4.0 < 2.4.2"
-
Affected