Google TensorFlow prior 2.4.4/2.5.2/2.6.1/2.7.0 SparseBinCount out-of-bounds

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

Summaryinfo

A vulnerability was found in Google TensorFlow. It has been declared as problematic. This vulnerability affects the function SparseBinCount. Executing a manipulation can lead to out-of-bounds. This vulnerability appears as CVE-2021-41226. The attack may be performed from remote. There is no available exploit. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability has been found in Google TensorFlow (Artificial Intelligence Software) and classified as critical. This vulnerability affects the function SparseBinCount. The manipulation with an unknown input leads to a out-of-bounds vulnerability. The CWE definition for the vulnerability is CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. As an impact it is known to affect confidentiality, integrity, and availability.

The weakness was presented 11/06/2021 as GHSA-374m-jm66-3vj8. The advisory is available at github.com. This vulnerability was named CVE-2021-41226 since 09/15/2021. Technical details are known, but there is no available exploit.

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

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

Vendor

Name

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.7
VulDB Meta Temp Score: 6.5

VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

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

CVSSv2info

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

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

Exploitinginfo

Class: Out-of-bounds
CWE: CWE-125 / CWE-119
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: f410212e373eb2aec4c9e60bf3702eba99a38aba

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-374m-jm66-3vj8
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2021-41226 (🔍)
GCVE (CVE): GCVE-0-2021-41226
GCVE (VulDB): GCVE-100-186178

Entryinfo

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

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!