2021-37680 | Google TensorFlow TFLite divide by zero

By Max On Aug 17, 2021

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.
4.1	$0-$5k	0.25

A vulnerability, which was classified as problematic, was found in Google TensorFlow up to 2.3.3/2.4.2/2.5.0 (Artificial Intelligence Software). This affects some unknown functionality of the component TFLite. The manipulation with an unknown input leads to a denial of service vulnerability. CWE is classifying the issue as CWE-369. This is going to have an impact on availability. The summary by CVE is:

TensorFlow is an end-to-end open source platform for machine learning. In affected versions the implementation of fully connected layers in TFLite is [vulnerable to a division by zero error](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/fully_connected.cc#L226). We have patched the issue in GitHub commit 718721986aa137691ee23f03638867151f74935f. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.

The weakness was disclosed 08/13/2021. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2021-37680 since 07/29/2021. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/17/2021).

Upgrading to version 2.3.4, 2.4.3, 2.5.1 or 2.6.0 eliminates this vulnerability. Applying a patch 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.

Type

Vendor

Name

VulDB Meta Base Score: 4.3
VulDB Meta Temp Score: 4.1

VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍

AV	AC	Au	C	I	A
🔍	🔍	🔍	🔍	🔍	🔍
🔍	🔍	🔍	🔍	🔍	🔍
🔍	🔍	🔍	🔍	🔍	🔍

Vector	Complexity	Authentication	Confidentiality	Integrity	Availability
unlock	unlock	unlock	unlock	unlock	unlock
unlock	unlock	unlock	unlock	unlock	unlock
unlock	unlock	unlock	unlock	unlock	unlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Class: Denial of service
CWE: CWE-369
ATT&CK: Unknown

Local: No
Remote: Yes

Availability: 🔒
Status: Not defined

Price Prediction: 🔍
Current Price Estimation: 🔒

0-Day	unlock	unlock	unlock	unlock
Today	unlock	unlock	unlock	unlock

Threat Intelligenceinfoedit

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: TensorFlow 2.3.4/2.4.3/2.5.1/2.6.0
Patch: github.com

07/29/2021 CVE assigned
08/13/2021 +15 days Advisory disclosed
08/13/2021 +0 days VulDB entry created
08/17/2021 +4 days VulDB last updateVendor: https://www.google.com/

Advisory: github.com
Status: Confirmed
Confirmation: 🔒

CVE: CVE-2021-37680 (🔒)

Created: 08/13/2021 07:31
Updated: 08/17/2021 21:46
Changes: (1) source_cve_cna
Complete: 🔍

Comments

Check our Alexa App!

Source link