Missing validation causes denial of service via `UnsortedSegmentJoin`
Impact
The implementation of tf.raw_ops.UnsortedSegmentJoin does not fully validate the input arguments. This results in a CHECK-failure which can be used to trigger a denial of service attack:
import tensorflow as tf
tf.raw_ops.UnsortedSegmentJoin(
inputs=tf.constant("this", shape=[12], dtype=tf.string),
segment_ids=tf.constant(0, shape=[12], dtype=tf.int64),
num_segments=tf.constant(0, shape=[12], dtype=tf.int64))The code assumes num_segments is a scalar but there is no validation for this before accessing its value:
const Tensor& num_segments_tensor = context->input(2);
OP_REQUIRES(context, num_segments_tensor.NumElements() != 0,
errors::InvalidArgument("Number of segments cannot be empty."));
auto num_segments = num_segments_tensor.scalar<NUM_SEGMENTS_TYPE>()();Patches
We have patched the issue in GitHub commit 13d38a07ce9143e044aa737cfd7bb759d0e9b400.
The fix will be included in TensorFlow 2.9.0. We will also cherrypick this commit on TensorFlow 2.8.1, TensorFlow 2.7.2, and TensorFlow 2.6.4, as these are also affected and still in supported range.
For more information
Please consult our security guide for more information regarding the security model and how to contact us with issues and questions.
Attribution
This vulnerability has been reported by Neophytos Christou from Secure Systems Lab at Brown University.
Software afectado
Haz clic en una tecnología para ver todas sus vulnerabilidades.
| Plataforma | Paquete | Versiones vulnerables | Corregida en |
|---|---|---|---|
| Python (PyPI) | tensorflow | < 2.6.4, >= 2.7.0, < 2.7.2, >= 2.8.0, < 2.8.1 | 2.6.4, 2.7.2, 2.8.1 |
| Python (PyPI) | tensorflow-cpu | < 2.6.4, >= 2.7.0, < 2.7.2, >= 2.8.0, < 2.8.1 | 2.6.4, 2.7.2, 2.8.1 |
| Python (PyPI) | tensorflow-gpu | < 2.6.4, >= 2.7.0, < 2.7.2, >= 2.8.0, < 2.8.1 | 2.6.4, 2.7.2, 2.8.1 |
Referencias
- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-hrg5-737c-2p56
- https://nvd.nist.gov/vuln/detail/CVE-2022-29197
- https://github.com/tensorflow/tensorflow/commit/13d38a07ce9143e044aa737cfd7bb759d0e9b400
- https://github.com/tensorflow/tensorflow
- https://github.com/tensorflow/tensorflow/blob/f3b9bf4c3c0597563b289c0512e98d4ce81f886e/tensorflow/core/kernels/unsorted_segment_join_op.cc#L92-L95
- https://github.com/tensorflow/tensorflow/releases/tag/v2.6.4
- https://github.com/tensorflow/tensorflow/releases/tag/v2.7.2
- https://github.com/tensorflow/tensorflow/releases/tag/v2.8.1
- https://github.com/tensorflow/tensorflow/releases/tag/v2.9.0
- https://pypi.org/project/tensorflow-gpu
- https://github.com/advisories/GHSA-hrg5-737c-2p56
- https://pypi.org/project/tensorflow
- https://pypi.org/project/tensorflow-cpu
- Vector CVSS
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H- Debilidad (CWE)
CWE-20- Plataforma
- Python (PyPI)
- Paquete
tensorflow, tensorflow-cpu, tensorflow-gpu- Publicada
- 24.05.2022
- Actualizado
- 11.10.2026 14:17
Fuentes y licencias
OSV / GitHub Advisory Database - PYSEC-2026-1009 - PyPA Advisory Database; CC BY 4.0
OSV / GitHub Advisory Database - PYSEC-2026-3202 - PyPA Advisory Database; CC BY 4.0
OSV / GitHub Advisory Database - GHSA-hrg5-737c-2p56 - CC BY 4.0
OSV / GitHub Advisory Database - PYSEC-2026-3341 - PyPA Advisory Database; CC BY 4.0
Historial de vulnerabilidades: tensorflow
Todas las vulnerabilidades publicadas de este paquete (Python (PyPI)), de la más reciente a la más antigua. Muestra si es un fallo aislado o un paquete que hay que vigilar.
- Entradas en total
- 433
- Primera → última
- 04.2019 07.2024
- Sin corrección
- 0
- Explotada en ataques
- 0
Distribución por gravedad
- Crítica 6
- Alta 112
- Media 210
- Baja 105
Divulgaciones por año
- 2019: 7
- 2020: 35
- 2021: 200
- 2022: 169
- 2023: 21
- 2024: 1
- 2025: 0
- 2026: 0
-
Missing validation causes denial of service via `UnsortedSegmentJoin` esta entrada
Identifica las vulnerabilidades de tu aplicación
Con la integración de DockRay y el inventario de software activado, DockRay compara las versiones notificadas de los componentes con las vulnerabilidades conocidas y avisa de las coincidencias confirmadas. La cobertura depende de la tecnología compatible y de los avisos disponibles.