Segmentation faultin TensorFlow when converting a Python string to `tf.float16`
Impact
Converting a string (from Python) to a tf.float16 value results in a segmentation fault in eager mode as the format checks for this use case are only in the graph mode.
This issue can lead to denial of service in inference/training where a malicious attacker can send a data point which contains a string instead of a tf.float16 value.
Similar effects can be obtained by manipulating saved models and checkpoints whereby replacing a scalar tf.float16 value with a scalar string will trigger this issue due to automatic conversions.
This can be easily reproduced by tf.constant("hello", tf.float16), if eager execution is enabled.
Patches
We have patched the vulnerability in GitHub commit 5ac1b9.
We are additionally releasing TensorFlow 1.15.1 and 2.0.1 with this vulnerability patched.
TensorFlow 2.1.0 was released after we fixed the issue, thus it is not affected.
We encourage users to switch to TensorFlow 1.15.1, 2.0.1 or 2.1.0.
For more information
Please consult SECURITY.md for more information regarding the security model and how to contact us with issues and questions.
Software afectado
Haz clic en una tecnología para ver todas sus vulnerabilidades.
| Plataforma | Paquete | Versiones vulnerables | Corregida en |
|---|---|---|---|
| Python (PyPI) | tensorflow | < 1.15.2, >= 2.0.0, < 2.0.1 | 1.15.2, 2.0.1 |
| Python (PyPI) | tensorflow-cpu | < 1.15.2, >= 2.0.0, < 2.0.1 | 1.15.2, 2.0.1 |
| Python (PyPI) | tensorflow-gpu | < 1.15.2, >= 2.0.0, < 2.0.1 | 1.15.2, 2.0.1 |
Referencias
- https://github.com/tensorflow/tensorflow/releases/tag/v1.15.2
- https://github.com/tensorflow/tensorflow/commit/5ac1b9e24ff6afc465756edf845d2e9660bd34bf
- https://github.com/tensorflow/tensorflow/releases/tag/v2.0.1
- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-977j-xj7q-2jr9
- https://nvd.nist.gov/vuln/detail/CVE-2020-5215
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2020-303.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2020-338.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2020-258.yaml
- https://github.com/tensorflow/tensorflow
- Vector CVSS
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:L- Debilidad (CWE)
CWE-754- Plataforma
- Python (PyPI)
- Paquete
tensorflow, tensorflow-cpu, tensorflow-gpu- Publicada
- 28.01.2020
- Actualizado
- 11.10.2026 15:17
Fuentes y licencias
OSV / GitHub Advisory Database - PYSEC-2020-258 - PyPA Advisory Database; CC BY 4.0
OSV / GitHub Advisory Database - PYSEC-2020-303 - PyPA Advisory Database; CC BY 4.0
OSV / GitHub Advisory Database - PYSEC-2020-338 - PyPA Advisory Database; CC BY 4.0
OSV / GitHub Advisory Database - GHSA-977j-xj7q-2jr9 - CC BY 4.0
Historial de vulnerabilidades: tensorflow-gpu
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
- 427
- Primera → última
- 04.2019 07.2024
- Sin corrección
- 0
- Explotada en ataques
- 0
Distribución por gravedad
- Crítica 6
- Alta 109
- Media 207
- Baja 105
Divulgaciones por año
- 2019: 7
- 2020: 35
- 2021: 200
- 2022: 166
- 2023: 18
- 2024: 1
- 2025: 0
- 2026: 0
-
Segmentation faultin TensorFlow when converting a Python string to `tf.float16` 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.