Google TensorFlow up to 2.1.3/2.2.2/2.3.2/2.4.1 dequantize_op.cc tf.raw_ops.Dequantize out-of-bounds
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.1 | $0-$5k | 0.00 |
Summary
A vulnerability described as problematic has been identified in Google TensorFlow up to 2.1.3/2.2.2/2.3.2/2.4.1. This affects the function tf.raw_ops.Dequantize of the file core/kernels/dequantize_op.cc. The manipulation results in out-of-bounds.
This vulnerability is cataloged as CVE-2021-29582. The attack may be launched remotely. There is no exploit available.
Upgrading the affected component is recommended.
Details
A vulnerability classified as problematic has been found in Google TensorFlow up to 2.1.3/2.2.2/2.3.2/2.4.1 (Artificial Intelligence Software). Affected is the function tf.raw_ops.Dequantize of the file core/kernels/dequantize_op.cc. 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 availability.
The weakness was shared 05/15/2021. The advisory is available at github.com. This vulnerability is traded as CVE-2021-29582. Successful exploitation requires user interaction by the victim. Technical details are known, but there is no available exploit.
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.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
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: Out-of-boundsCWE: CWE-125 / CWE-119
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/19/2021 🔍
Sources
Vendor: google.comAdvisory: github.com
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2021-29582 (🔍)
GCVE (CVE): GCVE-0-2021-29582
GCVE (VulDB): GCVE-100-175194
Entry
Created: 05/15/2021 17:30Updated: 05/19/2021 16:33
Changes: 05/15/2021 17:30 (41), 05/19/2021 16:25 (6), 05/19/2021 16:33 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.