Google TensorFlow up to 2.1.3/2.2.2/2.3.2/2.4.1 quantize_and_dequantize_op.cc tf.raw_ops.QuantizeAndDequantizeV2 initialization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.7 | $0-$5k | 0.00 |
Summary
A vulnerability described as critical has been identified in Google TensorFlow up to 2.1.3/2.2.2/2.3.2/2.4.1. Affected by this vulnerability is the function tf.raw_ops.QuantizeAndDequantizeV2 of the file core/kernels/quantize_and_dequantize_op.cc. Such manipulation leads to initialization.
This vulnerability is listed as CVE-2021-29610. The attack may be performed from remote. There is no available exploit.
Upgrading the affected component is recommended.
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) and classified as critical. Affected by this issue is the function tf.raw_ops.QuantizeAndDequantizeV2 of the file core/kernels/quantize_and_dequantize_op.cc. The manipulation with an unknown input leads to a initialization vulnerability. Using CWE to declare the problem leads to CWE-665. The product does not initialize or incorrectly initializes a resource, which might leave the resource in an unexpected state when it is accessed or used. Impacted is confidentiality, integrity, and availability.
The weakness was presented 05/15/2021. The advisory is shared for download at github.com. This vulnerability is handled as CVE-2021-29610. 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: 7.0VulDB Meta Temp Score: 6.9
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.8
NVD Vector: 🔍
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: InitializationCWE: CWE-665
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.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-29610 (🔍)
GCVE (CVE): GCVE-0-2021-29610
GCVE (VulDB): GCVE-100-175208
Entry
Created: 05/15/2021 18:14Updated: 05/19/2021 20:01
Changes: 05/15/2021 18:14 (41), 05/19/2021 19:54 (6), 05/19/2021 20:01 (19)
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.