Google TensorFlow up to 2.1.3/2.2.2/2.3.2/2.4.1 ctc_decoder_ops.cc tf.raw_ops.CTCBeamSearchDecoder uninitialized resource

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

Summaryinfo

A vulnerability marked as problematic has been reported in Google TensorFlow up to 2.1.3/2.2.2/2.3.2/2.4.1. The impacted element is the function tf.raw_ops.CTCBeamSearchDecoder of the file /core/kernels/ctc_decoder_ops.cc. The manipulation leads to uninitialized resource. This vulnerability is listed as CVE-2021-29581. The attack may be initiated remotely. There is no available exploit. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability was found in Google TensorFlow up to 2.1.3/2.2.2/2.3.2/2.4.1 (Artificial Intelligence Software). It has been rated as problematic. This issue affects the function tf.raw_ops.CTCBeamSearchDecoder of the file /core/kernels/ctc_decoder_ops.cc. The manipulation with an unknown input leads to a uninitialized resource vulnerability. Using CWE to declare the problem leads to CWE-908. The product uses or accesses a resource that has not been initialized. Impacted is availability.

The weakness was presented 05/15/2021. The advisory is shared at github.com. The identification of this vulnerability is CVE-2021-29581. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.

Upgrading to version 2.1.4, 2.2.3, 2.3.3, 2.4.2 or 2.5.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.

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

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

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: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Uninitialized resource
CWE: CWE-908
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
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.1.4/2.2.3/2.3.3/2.4.2/2.5.0
Patch: github.com

Timelineinfo

03/30/2021 🔍
05/15/2021 +46 days 🔍
05/15/2021 +0 days 🔍
05/19/2021 +4 days 🔍

Sourcesinfo

Vendor: google.com

Advisory: github.com
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2021-29581 (🔍)
GCVE (CVE): GCVE-0-2021-29581
GCVE (VulDB): GCVE-100-175193

Entryinfo

Created: 05/15/2021 17:29
Updated: 05/19/2021 16:18
Changes: 05/15/2021 17:29 (41), 05/19/2021 16:10 (6), 05/19/2021 16:18 (1)
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!