Google TensorFlow prior 2.4.4/2.5.2/2.6.1/2.7.0 Convolution Operator divide by zero

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.8$0-$5k0.00

Summaryinfo

A vulnerability identified as problematic has been detected in Google TensorFlow. Affected by this vulnerability is an unknown functionality of the component Convolution Operator. Performing a manipulation results in divide by zero. This vulnerability was named CVE-2021-41209. The attack may be initiated remotely. There is no available exploit. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in Google TensorFlow (Artificial Intelligence Software). It has been classified as problematic. This affects some unknown functionality of the component Convolution Operator. The manipulation with an unknown input leads to a divide by zero vulnerability. CWE is classifying the issue as CWE-369. The product divides a value by zero. This is going to have an impact on availability.

The weakness was presented 11/06/2021 as GHSA-6hpv-v2rx-c5g6. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2021-41209 since 09/15/2021. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1499 for this issue.

Upgrading to version 2.4.4, 2.5.2, 2.6.1 or 2.7.0 eliminates this vulnerability. Applying the patch f2c3931113eaafe9ef558faaddd48e00a6606235 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.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

Vendor

Name

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.9
VulDB Meta Temp Score: 4.8

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

CNA Base Score: 5.5
CNA Vector (GitHub, Inc.): 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Divide by zero
CWE: CWE-369 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: TensorFlow 2.4.4/2.5.2/2.6.1/2.7.0
Patch: f2c3931113eaafe9ef558faaddd48e00a6606235

Timelineinfo

09/15/2021 🔍
11/06/2021 +52 days 🔍
11/06/2021 +0 days 🔍
11/10/2021 +4 days 🔍

Sourcesinfo

Vendor: google.com

Advisory: GHSA-6hpv-v2rx-c5g6
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2021-41209 (🔍)
GCVE (CVE): GCVE-0-2021-41209
GCVE (VulDB): GCVE-100-186153

Entryinfo

Created: 11/06/2021 08:37
Updated: 11/10/2021 09:05
Changes: 11/06/2021 08:37 (52), 11/10/2021 09:05 (2)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!