Crash when type cannot be specialized in Tensorflow
Impact
Under certain scenarios, TensorFlow can fail to specialize a type during shape inference:
void InferenceContext::PreInputInit(
const OpDef& op_def, const std::vector<const Tensor*>& input_tensors,
const std::vector<ShapeHandle>& input_tensors_as_shapes) {
const auto ret = full_type::SpecializeType(attrs_, op_def);
DCHECK(ret.status().ok()) << "while instantiating types: " << ret.status();
ret_types_ = ret.ValueOrDie();
// ...
}However, DCHECK is a no-op in production builds and an assertion failure in debug builds. In the first case execution proceeds to the ValueOrDie line. This results in an assertion failure as ret contains an error Status, not a value. In the second case we also get a crash due to the assertion failure.
Patches
We have patched the issue in GitHub commit cb164786dc891ea11d3a900e90367c339305dc7b.
The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, and TensorFlow 2.6.3, 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.
Software afectado
Haz clic en una tecnología para ver todas sus vulnerabilidades.
| Plataforma | Paquete | Versiones vulnerables | Corregida en |
|---|---|---|---|
| Python (PyPI) | tensorflow | < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 | 2.5.3, 2.6.3, 2.7.1 |
| Python (PyPI) | tensorflow-cpu | < 2.5.3, >= 2.6.0, < 2.6.3 | 2.5.3, 2.6.3 |
| Python (PyPI) | tensorflow-gpu | < 2.5.3, >= 2.6.0, < 2.6.3 | 2.5.3, 2.6.3 |
Referencias
- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-rww7-2gpw-fv6j
- https://nvd.nist.gov/vuln/detail/CVE-2022-23572
- https://github.com/tensorflow/tensorflow/commit/cb164786dc891ea11d3a900e90367c339305dc7b
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2022-81.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2022-136.yaml
- https://github.com/tensorflow/tensorflow
- https://github.com/tensorflow/tensorflow/blob/a1320ec1eac186da1d03f033109191f715b2b130/tensorflow/core/framework/shape_inference.cc#L168-L174
- https://pypi.org/project/tensorflow
- https://github.com/advisories/GHSA-rww7-2gpw-fv6j
- Vector CVSS
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H- Debilidad (CWE)
CWE-617, CWE-754- Plataforma
- Python (PyPI)
- Paquete
tensorflow, tensorflow-cpu, tensorflow-gpu- Publicada
- 04.02.2022
- Actualizado
- 11.10.2026 14:17
Fuentes y licencias
OSV / GitHub Advisory Database - PYSEC-2022-81 - PyPA Advisory Database; CC BY 4.0
OSV / GitHub Advisory Database - PYSEC-2022-136 - PyPA Advisory Database; CC BY 4.0
OSV / GitHub Advisory Database - GHSA-rww7-2gpw-fv6j - CC BY 4.0
OSV / GitHub Advisory Database - PYSEC-2026-3241 - PyPA Advisory Database; CC BY 4.0
Historial de vulnerabilidades: tensorflow-cpu
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
- 430
- Primera → última
- 04.2019 07.2024
- Sin corrección
- 0
- Explotada en ataques
- 0
Distribución por gravedad
- Crítica 6
- Alta 111
- Media 208
- Baja 105
Divulgaciones por año
- 2019: 7
- 2020: 35
- 2021: 200
- 2022: 166
- 2023: 21
- 2024: 1
- 2025: 0
- 2026: 0
-
Crash when type cannot be specialized in Tensorflow 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.