Google TensorFlow prior 2.4.4/2.5.2/2.6.1/2.7.0 API tf.function locking
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in Google TensorFlow. This vulnerability affects the function tf.function of the component API. This manipulation causes locking.
This vulnerability is registered as CVE-2021-41213. Remote exploitation of the attack is possible. No exploit is available.
It is advisable to upgrade the affected component.
Details
A vulnerability was found in Google TensorFlow (Artificial Intelligence Software). It has been declared as problematic. Affected by this vulnerability is the function tf.function of the component API. The manipulation with an unknown input leads to a locking vulnerability. The CWE definition for the vulnerability is CWE-667. The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors. As an impact it is known to affect availability.
The weakness was published 11/06/2021 as GHSA-h67m-xg8f-fxcf. The advisory is shared at github.com. This vulnerability is known as CVE-2021-41213 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 afac8158d43691661ad083f6dd9e56f327c1dcb7 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.
Product
Type
Vendor
Name
License
Website
- Vendor: https://www.google.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.9VulDB 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.): 🔍
CVSSv2
| 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: 🔍
Exploiting
Class: LockingCWE: CWE-667
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: TensorFlow 2.4.4/2.5.2/2.6.1/2.7.0
Patch: afac8158d43691661ad083f6dd9e56f327c1dcb7
Timeline
09/15/2021 🔍11/06/2021 🔍
11/06/2021 🔍
11/10/2021 🔍
Sources
Vendor: google.comAdvisory: GHSA-h67m-xg8f-fxcf
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2021-41213 (🔍)
GCVE (CVE): GCVE-0-2021-41213
GCVE (VulDB): GCVE-100-186145
Entry
Created: 11/06/2021 06:36Updated: 11/10/2021 08:43
Changes: 11/06/2021 06:36 (53), 11/10/2021 08:43 (2)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.