Missing validation causes denial of service via `Conv3DBackpropFilterV2`
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.strings.unsorted_segment_join(
inputs=['123'],
segment_ids=[0],
num_segments=-1)
The code assumes num_segments is a positive scalar but there is no validation:
const Tensor& num_segments_tensor = context->input(2);
auto num_segments = num_segments_tensor.scalar<NUM_SEGMENTS_TYPE>()();
// ...
Tensor* output_tensor = nullptr;
TensorShape output_shape =
GetOutputShape(input_shape, segment_id_shape, num_segments);
Since this value is used to allocate the output tensor, a negative value would result in a CHECK-failure (assertion failure), as per TFSA-2021-198.
Patches
We have patched the issue in GitHub commit 84563f265f28b3c36a15335c8b005d405260e943 and GitHub commit 20cb18724b0bf6c09071a3f53434c4eec53cc147.
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 externally via a GitHub issue.
Czego dotyczy
Kliknij technologię, aby zobaczyć wszystkie dotyczące jej podatności.
| Platforma | Paczka | Podatne wersje | Poprawka w wersji |
|---|---|---|---|
| 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 |
Odnośniki
- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-hx9q-2mx4-m4pg
- https://nvd.nist.gov/vuln/detail/CVE-2022-29204
- https://github.com/tensorflow/tensorflow/commit/20cb18724b0bf6c09071a3f53434c4eec53cc147
- https://github.com/tensorflow/tensorflow/commit/84563f265f28b3c36a15335c8b005d405260e943
- https://github.com/tensorflow/tensorflow
- https://github.com/tensorflow/tensorflow/blob/f3b9bf4c3c0597563b289c0512e98d4ce81f886e/tensorflow/core/kernels/unsorted_segment_join_op.cc#L83-L14
- https://github.com/tensorflow/tensorflow/blob/master/tensorflow/security/advisory/tfsa-2021-198.md
- 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-hx9q-2mx4-m4pg
- https://pypi.org/project/tensorflow
- https://pypi.org/project/tensorflow-cpu
- Wektor CVSS
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H- Słabość (CWE)
CWE-191, CWE-20- Platforma
- Python (PyPI)
- Paczka
tensorflow, tensorflow-cpu, tensorflow-gpu- Ujawniono
- 24.05.2022
- Aktualizacja
- 11.10.2026 14:18
Źródła i licencje
OSV / GitHub Advisory Database - PYSEC-2026-1010 - PyPA Advisory Database; CC BY 4.0
OSV / GitHub Advisory Database - PYSEC-2026-3203 - PyPA Advisory Database; CC BY 4.0
OSV / GitHub Advisory Database - GHSA-hx9q-2mx4-m4pg - CC BY 4.0
OSV / GitHub Advisory Database - PYSEC-2026-3342 - PyPA Advisory Database; CC BY 4.0
Historia podatności: tensorflow-cpu
Wszystkie opisane podatności tej paczki (Python (PyPI)), od najnowszej. Widać, czy to jednorazowa wpadka, czy paczka, której trzeba pilnować.
- Wszystkich wpisów
- 430
- Pierwsza → ostatnia
- 04.2019 07.2024
- Bez poprawki
- 0
- Wykorzystywana w atakach
- 0
Rozkład istotności
- Krytyczna 6
- Wysoka 111
- Średnia 208
- Niska 105
Ujawnienia w latach
- 2019: 7
- 2020: 35
- 2021: 200
- 2022: 166
- 2023: 21
- 2024: 1
- 2025: 0
- 2026: 0
-
Missing validation causes denial of service via `Conv3DBackpropFilterV2` ten wpis
Dowiedz się, które podatności dotyczą Twojej aplikacji
Po podłączeniu integracji DockRay i włączeniu raportowania oprogramowania DockRay porównuje zgłoszone wersje komponentów ze znanymi podatnościami i powiadamia o potwierdzonych dopasowaniach. Zakres zależy od obsługiwanej technologii i dostępnych biuletynów.