nday
CVE-2021-37641 GHSA-9c8h-vvrj-w2p8

Heap OOB in `RaggedGather` in TensorFlow

tensorflow / tensorflow

Fecha de divulgación: . nday aún no tiene constancia de una corrección; eso no significa que no exista parche. Ninguna de las cuatro fuentes de PoC la recoge. No figura en el KEV de CISA.

why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

out-of-bounds read
CWE-125, stated by the CNA GitHub_M y NVD, republishing [email protected]
local
AV:L in CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H (CVSS 3.1) from the CNA GitHub_M
no user interaction
UI:N in CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H (CVSS 3.1) from the CNA GitHub_M
TensorFlow
affected products in the CVE record: tensorflow · tensorflowCPE names NVD's analysts give as vulnerable: a:google:tensorflow
AI / ML
affected products in the CVE record: tensorflow · tensorflowCPE names NVD's analysts give as vulnerable: a:google:tensorflowthe product type of TensorFlow in nday's product registry
open-source library / framework
affected products in the CVE record: tensorflow · tensorflowCPE names NVD's analysts give as vulnerable: a:google:tensorflowthe product type of TensorFlow in nday's product registry
etapa
DIS
divulgación
cvss
7.3 HIGH v3.1

Ciclo de vida

Eje x en UTC; punto = minuto exacto, barra ancha = solo fecha, hueco = desconocida o inferida.
fecha desconocida
DISdivulgada
2021-08-12T20:30Z
PATparcheada
sin registro aún
ANAanalizada
sin registro aún
POCPoC
sin registro aún
ITWexplotada
sin registro aún
KEVen KEV
sin registro aún

Descripción

TensorFlow is an end-to-end open source platform for machine learning. In affected versions if the arguments to tf.raw_ops.RaggedGather don't determine a valid ragged tensor code can trigger a read from outside of bounds of heap allocated buffers. The [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/ragged_gather_op.cc#L70) directly reads the first dimension of a tensor shape before checking that said tensor has rank of at least 1 (i.e., it is not a scalar). Furthermore, the implementation does not check that the list given by params_nested_splits is not an empty list of tensors. We have patched the issue in GitHub commit a2b743f6017d7b97af1fe49087ae15f0ac634373. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.

Original text of the CVE record (cvelist), shown as published.

Exploit conditions

What an attack needs, read from the CVSS vector.
Attack vector AV:L
Local: needs a local or SSH session, or a user tricked into acting on the machine
Attack complexity AC:L
Low: no special conditions; the attacker can expect repeatable success
Privileges required PR:L
Low: ordinary user privileges
User interaction UI:N
None: no action by anyone other than the attacker

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H

CVSS 3.1 vector from the CVE record, scored by the CNA GitHub_M.

Registro de eventos

+DISdivulgación

GitHub_M publicó el registro CVE. CVSS 7.3, severidad alta.

fuente cvelist · nday , importación masiva · en bruto
{
  "id": 246725,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2021-37641",
  "occurred_at": "2021-08-12T20:30:17Z",
  "observed_at": "2026-11-13T05:37:27.583528Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "cvss": {
      "source": "cna",
      "vector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H",
      "version": "3.1",
      "base_score": 7.3,
      "base_severity": "HIGH"
    },
    "state": "PUBLISHED",
    "date_published": "2021-08-12T20:30:17.000Z",
    "assigner_short_name": "GitHub_M"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Debate de investigadores

0 investigadores lo mencionaron en los últimos 7 días

Publicaciones en X de investigadores de la lista de nday que mencionan este CVE, tal como se publicaron. nday no las verifica.

nday aún no ha recopilado publicaciones en X de investigadores de su lista sobre este CVE.

Discussion

0 comments

No comments yet.