Undefined behavior when users supply invalid resource handles
Impact
Multiple TensorFlow operations misbehave in eager mode when the resource handle provided to them is invalid:
import tensorflow as tf
tf.raw_ops.QueueIsClosedV2(handle=[])import tensorflow as tf
tf.summary.flush(writer=())In graph mode, it would have been impossible to perform these API calls, but migration to TF 2.x eager mode opened up this vulnerability. If the resource handle is empty, then a reference is bound to a null pointer inside TensorFlow codebase (various codepaths). This is undefined behavior.
Patches
We have patched the issue in GitHub commit a5b89cd68c02329d793356bda85d079e9e69b4e7 and GitHub commit dbdd98c37bc25249e8f288bd30d01e118a7b4498.
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 Hong Jin from Singapore Management University.
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-5wpj-c6f7-24x8
- https://nvd.nist.gov/vuln/detail/CVE-2022-29207
- https://github.com/tensorflow/tensorflow/commit/a5b89cd68c02329d793356bda85d079e9e69b4e7
- https://github.com/tensorflow/tensorflow/commit/dbdd98c37bc25249e8f288bd30d01e118a7b4498
- https://github.com/tensorflow/tensorflow
- 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
- https://github.com/advisories/GHSA-5wpj-c6f7-24x8
- https://pypi.org/project/tensorflow-cpu
- https://pypi.org/project/tensorflow-gpu
- 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-20, CWE-475- 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-3112 - PyPA Advisory Database; CC BY 4.0
OSV / GitHub Advisory Database - PYSEC-2026-3280 - PyPA Advisory Database; CC BY 4.0
OSV / GitHub Advisory Database - GHSA-5wpj-c6f7-24x8 - CC BY 4.0
OSV / GitHub Advisory Database - PYSEC-2026-955 - PyPA Advisory Database; CC BY 4.0
Historia podatności: tensorflow-gpu
Wszystkie opisane podatności tej paczki (Python (PyPI)), od najnowszej. Widać, czy to jednorazowa wpadka, czy paczka, której trzeba pilnować.
- Wszystkich wpisów
- 427
- Pierwsza → ostatnia
- 04.2019 07.2024
- Bez poprawki
- 0
- Wykorzystywana w atakach
- 0
Rozkład istotności
- Krytyczna 6
- Wysoka 109
- Średnia 207
- Niska 105
Ujawnienia w latach
- 2019: 7
- 2020: 35
- 2021: 200
- 2022: 166
- 2023: 18
- 2024: 1
- 2025: 0
- 2026: 0
-
Undefined behavior when users supply invalid resource handles 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.