Google TensorFlow up to 2.1.3/2.2.2/2.3.2/2.4.1 sparse_tensors_map_ops.cc tf.raw_ops.AddManySparseToTensorsMap integer overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.1 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, was found in Google TensorFlow up to 2.1.3/2.2.2/2.3.2/2.4.1. This affects the function tf.raw_ops.AddManySparseToTensorsMap of the file core/kernels/sparse_tensors_map_ops.cc. The manipulation results in integer overflow.
This vulnerability was named CVE-2021-29523. The attack may be performed from remote. There is no available exploit.
You should upgrade the affected component.
Details
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 classified as problematic. Affected is the function tf.raw_ops.AddManySparseToTensorsMap of the file core/kernels/sparse_tensors_map_ops.cc. The manipulation with an unknown input leads to a integer overflow vulnerability. CWE is classifying the issue as CWE-190. The product performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the original value. This can introduce other weaknesses when the calculation is used for resource management or execution control. This is going to have an impact on availability.
The weakness was presented 05/15/2021. The advisory is shared for download at github.com. This vulnerability is traded as CVE-2021-29523. Successful exploitation requires user interaction by the victim. There are known technical details, 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.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.google.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: Integer overflowCWE: CWE-190 / CWE-189
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
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.1.4/2.2.3/2.3.3/2.4.2/2.5.0
Patch: github.com
Timeline
03/30/2021 🔍05/15/2021 🔍
05/15/2021 🔍
05/16/2021 🔍
Sources
Vendor: google.comAdvisory: github.com
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2021-29523 (🔍)
GCVE (CVE): GCVE-0-2021-29523
GCVE (VulDB): GCVE-100-175128
Entry
Created: 05/15/2021 08:43Updated: 05/16/2021 21:42
Changes: 05/15/2021 08:43 (41), 05/16/2021 21:31 (6), 05/16/2021 21:42 (1)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.