Google TensorFlow up to 2.7.1/2.8.0/2.9.0 list_kernels.cc TensorListReserve num_elements assertion
|CVSS Meta Temp Score|
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
|Current Exploit Price (≈)|
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
|CTI Interest Score|
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
A vulnerability was found in Google TensorFlow up to 2.7.1/2.8.0/2.9.0 (Artificial Intelligence Software). It has been classified as problematic. This affects the function
TensorListReserve of the file core/kernels/list_kernels.cc. The manipulation of the argument
num_elements with an unknown input leads to a assertion vulnerability. CWE is classifying the issue as CWE-617. The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary. This is going to have an impact on availability. The summary by CVE is:
TensorFlow is an open source platform for machine learning. In `core/kernels/list_kernels.cc's TensorListReserve`, `num_elements` is assumed to be a tensor of size 1. When a `num_elements` of more than 1 element is provided, then `tf.raw_ops.TensorListReserve` fails the `CHECK_EQ` in `CheckIsAlignedAndSingleElement`. We have patched the issue in GitHub commit b5f6fbfba76576202b72119897561e3bd4f179c7. 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 disclosed 09/17/2022 as GHSA-v5xg-3q2c-c2r4. It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2022-35960 since 07/15/2022. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/19/2022).
Upgrading to version 2.7.2, 2.8.1, 2.9.1 or 2.10.0 eliminates this vulnerability. Applying the patch b5f6fbfba76576202b72119897561e3bd4f179c7 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.
CVSSv3VulDB Meta Base Score: 5.7
VulDB Meta Temp Score: 5.7
VulDB Base Score: 3.7
VulDB Temp Score: 3.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CNA Base Score: 5.9
CNA Vector (GitHub, Inc.): 🔍
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
Threat IntelligenceInterest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
0-Day Time: 🔍
Upgrade: TensorFlow 2.7.2/2.8.1/2.9.1/2.10.0
09/17/2022 +64 days 🔍
09/17/2022 +0 days 🔍
10/19/2022 +32 days 🔍
CVE: CVE-2022-35960 (🔍)
EntryCreated: 09/17/2022 08:08 AM
Updated: 10/19/2022 02:31 PM
Changes: 09/17/2022 08:08 AM (55), 10/19/2022 02:31 PM (11)
Want to stay up to date on a daily basis?
Enable the mail alert feature now!