// For flags

CVE-2022-36017

Segfault in `Requantize` in TensorFlow

Severity Score

7.5
*CVSS v3.1

Exploit Likelihood

*EPSS

Affected Versions

*CPE

Public Exploits

0
*Multiple Sources

Exploited in Wild

-
*KEV

Decision

-
*SSVC
Descriptions

TensorFlow is an open source platform for machine learning. If `Requantize` is given `input_min`, `input_max`, `requested_output_min`, `requested_output_max` tensors of a nonzero rank, it results in a segfault that can be used to trigger a denial of service attack. We have patched the issue in GitHub commit 785d67a78a1d533759fcd2f5e8d6ef778de849e0. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue.

TensorFlow es una plataforma de código abierto para el aprendizaje automático. Si a "Requantize" le son dados los tensores "input_min", "input_max", "requested_output_min", "requested_output_max" de un rango distinto de cero, resulta en un segfault que puede usarse para desencadenar un ataque de denegación de servicio. Hemos parcheado el problema en el commit 785d67a78a1d533759fcd2f5e8d6ef778de849e0 de GitHub. La corrección será incluida en TensorFlow versión 2.10.0. También seleccionaremos este compromiso en TensorFlow versión 2.9.1, TensorFlow versión 2.8.1, y TensorFlow versión 2.7.2, ya que estos también están afectados y todavía están en el rango admitido. No se presentan mitigaciones conocidas para este problema

*Credits: N/A
CVSS Scores
Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High
Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High
* Common Vulnerability Scoring System
SSVC
  • Decision:-
Exploitation
-
Automatable
-
Tech. Impact
-
* Organization's Worst-case Scenario
Timeline
  • 2022-07-15 CVE Reserved
  • 2022-09-16 CVE Published
  • 2024-04-08 EPSS Updated
  • 2024-08-03 CVE Updated
  • ---------- Exploited in Wild
  • ---------- KEV Due Date
  • ---------- First Exploit
CWE
  • CWE-20: Improper Input Validation
CAPEC
Affected Vendors, Products, and Versions
Vendor Product Version Other Status
Vendor Product Version Other Status <-- --> Vendor Product Version Other Status
Google
Search vendor "Google"
Tensorflow
Search vendor "Google" for product "Tensorflow"
< 2.7.2
Search vendor "Google" for product "Tensorflow" and version " < 2.7.2"
-
Affected
Google
Search vendor "Google"
Tensorflow
Search vendor "Google" for product "Tensorflow"
>= 2.8.0 < 2.8.1
Search vendor "Google" for product "Tensorflow" and version " >= 2.8.0 < 2.8.1"
-
Affected
Google
Search vendor "Google"
Tensorflow
Search vendor "Google" for product "Tensorflow"
>= 2.9.0 < 2.9.1
Search vendor "Google" for product "Tensorflow" and version " >= 2.9.0 < 2.9.1"
-
Affected
Google
Search vendor "Google"
Tensorflow
Search vendor "Google" for product "Tensorflow"
2.10
Search vendor "Google" for product "Tensorflow" and version "2.10"
rc0
Affected
Google
Search vendor "Google"
Tensorflow
Search vendor "Google" for product "Tensorflow"
2.10
Search vendor "Google" for product "Tensorflow" and version "2.10"
rc1
Affected
Google
Search vendor "Google"
Tensorflow
Search vendor "Google" for product "Tensorflow"
2.10
Search vendor "Google" for product "Tensorflow" and version "2.10"
rc2
Affected
Google
Search vendor "Google"
Tensorflow
Search vendor "Google" for product "Tensorflow"
2.10
Search vendor "Google" for product "Tensorflow" and version "2.10"
rc3
Affected