Google TensorFlow prior 2.4.4/2.5.2/2.6.1/2.7.0 tf.ragged.cross out-of-bounds
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.5 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in Google TensorFlow. Impacted is the function tf.ragged.cross. This manipulation causes out-of-bounds.
The identification of this vulnerability is CVE-2021-41212. It is possible to initiate the attack remotely. There is no exploit available.
It is suggested to upgrade the affected component.
Details
A vulnerability has been found in Google TensorFlow (Artificial Intelligence Software) and classified as critical. Affected by this vulnerability is the function tf.ragged.cross. 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 shared 11/06/2021 as GHSA-fr77-rrx3-cp7g. The advisory is shared at github.com. This vulnerability is known as CVE-2021-41212 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 fa6b7782fbb14aa08d767bc799c531f5e1fb3bb8 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: 6.7VulDB 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.): 🔍
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: Out-of-boundsCWE: 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-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: fa6b7782fbb14aa08d767bc799c531f5e1fb3bb8
Timeline
09/15/2021 🔍11/06/2021 🔍
11/06/2021 🔍
11/10/2021 🔍
Sources
Vendor: google.comAdvisory: GHSA-fr77-rrx3-cp7g
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2021-41212 (🔍)
GCVE (CVE): GCVE-0-2021-41212
GCVE (VulDB): GCVE-100-186169
Entry
Created: 11/06/2021 09:34Updated: 11/10/2021 10:03
Changes: 11/06/2021 09:34 (52), 11/10/2021 10:03 (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.