Alta

Type confusion leading to segfault in Tensorflow

  • Publicada: 03.02.2022
  • Actualizado: 11.10.2026 15:17

Impact

The implementation of shape inference for ConcatV2 can be used to trigger a denial of service attack via a segfault caused by a type confusion:

python
import tensorflow as tf

@tf.function
def test():
  y = tf.raw_ops.ConcatV2(
    values=[[1,2,3],[4,5,6]],
    axis = 0xb500005b)
  return y

test()

The axis argument is translated into concat_dim in the ConcatShapeHelper helper function. Then, a value for min_rank is computed based on concat_dim. This is then used to validate that the values tensor has at least the required rank:

cc
  int64_t concat_dim;
  if (concat_dim_t->dtype() == DT_INT32) {
    concat_dim = static_cast<int64_t>(concat_dim_t->flat<int32>()(0));
  } else {
    concat_dim = concat_dim_t->flat<int64_t>()(0);
  }

  // Minimum required number of dimensions.
  const int min_rank = concat_dim < 0 ? -concat_dim : concat_dim + 1;

  // ...
  ShapeHandle input = c->input(end_value_index - 1);
  TF_RETURN_IF_ERROR(c->WithRankAtLeast(input, min_rank, &input));

However, WithRankAtLeast receives the lower bound as a 64-bits value and then compares it against the maximum 32-bits integer value that could be represented:

cc
Status InferenceContext::WithRankAtLeast(ShapeHandle shape, int64_t rank,
                                         ShapeHandle* out) {
  if (rank > kint32max) {
    return errors::InvalidArgument("Rank cannot exceed kint32max");
  }
  // ...
}

Due to the fact that min_rank is a 32-bits value and the value of axis, the rank argument is a negative value, so the error check is bypassed.

Patches

We have patched the issue in GitHub commit 08d7b00c0a5a20926363849f611729f53f3ec022.

The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.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.

Attribution

This vulnerability has been reported by Yu Tian of Qihoo 360 AIVul Team.

Software afectado

Haz clic en una tecnología para ver todas sus vulnerabilidades.

PlataformaPaqueteVersiones vulnerablesCorregida 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.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
Python (PyPI) tensorflow-gpu < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1

Referencias

Puntuación CVSS 6.5/10
Vector CVSS
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Debilidad (CWE)
CWE-754, CWE-843
Plataforma
Python (PyPI)
Paquete
tensorflow, tensorflow-cpu, tensorflow-gpu
Publicada
03.02.2022
Actualizado
11.10.2026 15:17

Fuentes y licencias

OSV / GitHub Advisory Database - PYSEC-2022-55 - PyPA Advisory Database; CC BY 4.0

OSV / GitHub Advisory Database - PYSEC-2022-110 - PyPA Advisory Database; CC BY 4.0

OSV / GitHub Advisory Database - PYSEC-2026-3211 - PyPA Advisory Database; CC BY 4.0

OSV / GitHub Advisory Database - GHSA-m4hf-j54p-p353 - 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.

Todas (433) en el archivo
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

  1. 2019: 7
  2. 2020: 35
  3. 2021: 200
  4. 2022: 169
  5. 2023: 21
  6. 2024: 1
  7. 2025: 0
  8. 2026: 0
Gravedad:
  1. Alta · 7.5 CVE-2023-33976 < 2.12.1 2.12.1
  2. Alta · 7.5 CVE-2023-25659 < 2.11.1 2.11.1
  3. Alta · 7.5 CVE-2023-25660 < 2.11.1 2.11.1
  4. Alta · 7.5 CVE-2023-25662 < 2.11.1 2.11.1
  5. Alta · 7.5 CVE-2023-25663 < 2.11.1 2.11.1
  6. Alta · 7.5 CVE-2023-25664 < 2.11.1 2.11.1
  7. Alta · 7.5 CVE-2023-25665 < 2.11.1 2.11.1
  8. Alta · 7.5 CVE-2023-25666 < 2.11.1 2.11.1
  9. Alta · 7.5 CVE-2023-25669 < 2.11.1 2.11.1
  10. Alta · 7.5 CVE-2023-25671 < 2.11.1 2.11.1
  11. Alta · 7.5 CVE-2023-25672 < 2.11.1 2.11.1
  12. Alta · 7.5 CVE-2023-25673 < 2.11.1 2.11.1
  13. Alta · 7.5 CVE-2023-25674 < 2.11.1 2.11.1
  14. Alta · 7.5 CVE-2023-25675 < 2.11.1 2.11.1
  15. Alta · 7.5 CVE-2023-25676 < 2.11.1 2.11.1
  16. Alta · 8.0 CVE-2023-25801 < 2.11.1 2.11.1
  17. Alta · 7.5 CVE-2023-27579 < 2.11.1 2.11.1
  18. Alta · 7.5 CVE-2023-25658 < 2.11.1 2.11.1
  19. Alta · 7.1 CVE-2022-41902 < 2.8.4, >= 2.9.0, < 2.9.3, >= 2.10.0, < 2.10.1 2.8.4, 2.9.3, 2.10.1
  20. Alta · 7.1 CVE-2022-41900 < 2.8.4, >= 2.9.0, < 2.9.3, >= 2.10.0, < 2.10.1 2.8.4, 2.9.3, 2.10.1
  21. Alta · 7.1 CVE-2022-41894 < 2.8.4, >= 2.9.0, < 2.9.3, >= 2.10.0, < 2.10.1 2.8.4, 2.9.3, 2.10.1
  22. Alta · 7.0 CVE-2022-35939 < 2.7.2, >= 2.8.0, < 2.8.1, >= 2.9.0, < 2.9.1 2.7.2, 2.8.1, 2.9.1
  23. Alta · 7.0 CVE-2022-35937 < 2.7.2, >= 2.8.0, < 2.8.1, >= 2.9.0, < 2.9.1 2.7.2, 2.8.1, 2.9.1
  24. Alta · 7.8 CVE-2022-29216 < 2.6.4, >= 2.7.0, < 2.7.2, >= 2.8.0, < 2.8.1 2.6.4, 2.7.2, 2.8.1
  25. Alta · 7.1 CVE-2022-29208 < 2.6.4, >= 2.7.0, < 2.7.2, >= 2.8.0, < 2.8.1 2.6.4, 2.7.2, 2.8.1
  26. Crítica · 9.3 ghsa-h6gw-r52c-724r < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  27. Alta · 7.0 ghsa-43q8-3fv7-pr5x < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  28. Alta · 8.8 CVE-2022-23594 >= 2.7.0, < 2.7.1 2.7.1
  29. Alta · 8.8 CVE-2022-23560 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  30. Alta · 7.1 CVE-2022-23563 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  31. Alta · 8.1 CVE-2022-23592 >= 2.8.0-rc0, < 2.8.0 2.8.0
  32. Alta · 7.5 CVE-2022-23591 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  33. Alta · 8.8 CVE-2022-23574 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  34. Alta · 7.6 CVE-2022-23573 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  35. Alta · 7.6 CVE-2022-23562 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  36. Alta · 8.8 CVE-2022-23561 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  37. Alta · 8.8 CVE-2022-23559 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  38. Alta · 8.8 CVE-2022-23566 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  39. Alta · 7.6 CVE-2022-23584 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  40. Alta · 7.6 CVE-2022-23558 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  41. Alta · 8.8 CVE-2022-23587 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  42. Alta · 7.6 CVE-2022-21740 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  43. Alta · 6.5 CVE-2022-21741 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  44. Alta · 6.5 CVE-2022-21739 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  45. Alta · 6.5 CVE-2022-21737 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  46. Alta · 6.5 CVE-2022-21738 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  47. Alta · 6.5 CVE-2022-23569 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  48. Alta · 6.5 CVE-2022-21729 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  49. Alta · 6.5 CVE-2022-21734 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  50. Alta · 6.5 CVE-2022-21735 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  51. Alta · 7.6 CVE-2022-21736 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  52. Type confusion leading to segfault in Tensorflow esta entrada
    Alta · 6.5 CVE-2022-21731 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  53. Alta · 6.5 CVE-2022-23567 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  54. Alta · 6.5 CVE-2022-23568 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  55. Alta · 8.1 CVE-2022-21726 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  56. Alta · 8.1 CVE-2022-21728 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  57. Alta · 7.6 CVE-2022-21727 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  58. Alta · 8.1 CVE-2022-21730 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
Mostrar más (20) Mostrando 60 de 118

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.

Conectar tu aplicación
Newsletter DockRay

La seguridad de tus aplicaciones en tu correo

Vulnerabilidades importantes, recomendaciones concretas y consejos prácticos para tus aplicaciones. Elige tus tecnologías y sigue lo que importa para tu proyecto.

  • Un resumen diario de nuevas vulnerabilidades, también las críticas.
  • Avisos sobre actualizaciones importantes.
  • Consejos prácticos sobre seguridad y monitorización de aplicaciones.

Déjalo vacío para recibir avisos de todas las tecnologías.

Suscripción gratuita. Date de baja con un clic en cualquier correo.