Google TensorFlow prior 2.4.4/2.5.2/2.6.1/2.7.0 SparseFillEmptyRows 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 classified as problematic. This affects the function SparseFillEmptyRows. Performing a manipulation results in out-of-bounds. This vulnerability is reported as CVE-2021-41224. The attack is possible to be carried out remotely. No exploit exists. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability, which was classified as critical, was found in Google TensorFlow (Artificial Intelligence Software). This affects the function SparseFillEmptyRows. The manipulation with an unknown input leads to a out-of-bounds vulnerability. CWE is classifying the issue as CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. This is going to have an impact on confidentiality, integrity, and availability.

The weakness was disclosed 11/06/2021 as GHSA-rg3m-hqc5-344v. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2021-41224 since 09/15/2021. Technical details are known, but no exploit is available.

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

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-rg3m-hqc5-344v
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2021-41224 (🔍)
GCVE (CVE): GCVE-0-2021-41224
GCVE (VulDB): GCVE-100-186177

Entryinfo

Created: 11/06/2021 09:39
Updated: 11/10/2021 10:48
Changes: 11/06/2021 09:39 (52), 11/10/2021 10:48 (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 ▸

Interested in the pricing of exploits?

See the underground prices here!