Google TensorFlow up to 2.7.1/2.8.0/2.9.0 Requantize denial of service

Summaryinfo

A vulnerability identified as problematic has been detected in Google TensorFlow up to 2.7.1/2.8.0/2.9.0. This affects the function Requantize. This manipulation of the argument input_min/input_max/requested_output_min/requested_output_max causes denial of service. This vulnerability appears as CVE-2022-36017. The attack may be initiated remotely. There is no available exploit. You should upgrade the affected component.

Detailsinfo

A vulnerability has been found in Google TensorFlow up to 2.7.1/2.8.0/2.9.0 (Artificial Intelligence Software) and classified as problematic. Affected by this vulnerability is the function Requantize. The manipulation of the argument input_min/input_max/requested_output_min/requested_output_max with an unknown input leads to a denial of service vulnerability. The CWE definition for the vulnerability is CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. As an impact it is known to affect availability. The summary by CVE is:

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.

The weakness was presented 09/17/2022 as GHSA-wqmc-pm8c-2jhc. It is possible to read the advisory at github.com. This vulnerability is known as CVE-2022-36017 since 07/15/2022. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1499 according to MITRE ATT&CK.

Upgrading to version 2.7.2, 2.8.1, 2.9.1 or 2.10.0 eliminates this vulnerability. Applying the patch 785d67a78a1d533759fcd2f5e8d6ef778de849e0 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Type

• Artificial Intelligence Software

Vendor

• Google

Name

• TensorFlow

Version

• 2.0
• 2.1
• 2.2
• 2.3
• 2.4
• 2.5
• 2.6
• 2.7
• 2.7.0
• 2.7.1
• 2.8
• 2.8.0
• 2.9.0

License

• free

Website

• Vendor: https://www.google.com/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion