`CHECK` fail via inputs in `SdcaOptimizer`
Impact
Inputs dense_features or example_state_data not of rank 2 will trigger a CHECK fail in SdcaOptimizer.
import tensorflow as tf
tf.raw_ops.SdcaOptimizer(
sparse_example_indices=4 * [tf.random.uniform([5,5,5,3], dtype=tf.dtypes.int64, maxval=100)],
sparse_feature_indices=4 * [tf.random.uniform([5,5,5,3], dtype=tf.dtypes.int64, maxval=100)],
sparse_feature_values=8 * [tf.random.uniform([5,5,5,3], dtype=tf.dtypes.float32, maxval=100)],
dense_features=4 * [tf.random.uniform([5,5,5,3], dtype=tf.dtypes.float32, maxval=100)],
example_weights=tf.random.uniform([5,5,5,3], dtype=tf.dtypes.float32, maxval=100),
example_labels=tf.random.uniform([5,5,5,3], dtype=tf.dtypes.float32, maxval=100),
sparse_indices=4 * [tf.random.uniform([5,5,5,3], dtype=tf.dtypes.int64, maxval=100)],
sparse_weights=4 * [tf.random.uniform([5,5,5,3], dtype=tf.dtypes.float32, maxval=100)],
dense_weights=4 * [tf.random.uniform([5,5,5,3], dtype=tf.dtypes.float32, maxval=100)],
example_state_data=tf.random.uniform([5,5,5,3], dtype=tf.dtypes.float32, maxval=100),
loss_type="squared_loss",
l1=0.0,
l2=0.0,
num_loss_partitions=1,
num_inner_iterations=1,
adaptative=False,)
Patches
We have patched the issue in GitHub commit 80ff197d03db2a70c6a111f97dcdacad1b0babfa.
The fix will be included in TensorFlow 2.11. We will also cherrypick this commit on TensorFlow 2.10.1, 2.9.3, and TensorFlow 2.8.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 Zizhuang Deng of IIE, UCAS
Software afectado
Haz clic en una tecnología para ver todas sus vulnerabilidades.
| Plataforma | Paquete | Versiones vulnerables | Corregida en |
|---|---|---|---|
| Python (PyPI) | tensorflow | < 2.8.4, >= 2.9.0, < 2.9.3, >= 2.10.0, < 2.10.1 | 2.8.4, 2.9.3, 2.10.1 |
| Python (PyPI) | tensorflow-cpu | < 2.8.4, >= 2.9.0, < 2.9.3, >= 2.10.0, < 2.10.1 | 2.8.4, 2.9.3, 2.10.1 |
| Python (PyPI) | tensorflow-gpu | < 2.8.4, >= 2.9.0, < 2.9.3, >= 2.10.0, < 2.10.1 | 2.8.4, 2.9.3, 2.10.1 |
Referencias
- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-27rc-728f-x5w2
- https://nvd.nist.gov/vuln/detail/CVE-2022-41899
- https://github.com/tensorflow/tensorflow/commit/80ff197d03db2a70c6a111f97dcdacad1b0babfa
- https://github.com/tensorflow/tensorflow
- https://github.com/tensorflow/tensorflow/blob/master/tensorflow/core/kernels/sdca_internal.cc
- https://pypi.org/project/tensorflow
- https://github.com/advisories/GHSA-27rc-728f-x5w2
- https://pypi.org/project/tensorflow-cpu
- https://pypi.org/project/tensorflow-gpu
- Vector CVSS
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:N/A:H- Debilidad (CWE)
CWE-20, CWE-617- Plataforma
- Python (PyPI)
- Paquete
tensorflow, tensorflow-cpu, tensorflow-gpu- Publicada
- 21.11.2022
- Actualizado
- 11.10.2026 14:17
Fuentes y licencias
OSV / GitHub Advisory Database - PYSEC-2026-3086 - PyPA Advisory Database; CC BY 4.0
OSV / GitHub Advisory Database - PYSEC-2026-3264 - PyPA Advisory Database; CC BY 4.0
OSV / GitHub Advisory Database - GHSA-27rc-728f-x5w2 - CC BY 4.0
OSV / GitHub Advisory Database - PYSEC-2026-941 - 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
-
`CHECK` fail via inputs in `SdcaOptimizer` 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.