Google TensorFlow up to 2.1.3/2.2.2/2.3.2/2.4.1 maxpooling_op.cc tf.raw_ops.MaxPoolGradWithArgmax divide by zero
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Google TensorFlow up to 2.1.3/2.2.2/2.3.2/2.4.1 and classified as problematic. Affected by this vulnerability is the function tf.raw_ops.MaxPoolGradWithArgmax of the file core/kernels/maxpooling_op.cc. Executing a manipulation can lead to divide by zero.
This vulnerability is handled as CVE-2021-29573. The attack can be executed remotely. There is not any exploit available.
It is suggested to upgrade the affected component.
Details
A vulnerability classified as problematic was found in Google TensorFlow up to 2.1.3/2.2.2/2.3.2/2.4.1 (Artificial Intelligence Software). This vulnerability affects the function tf.raw_ops.MaxPoolGradWithArgmax of the file core/kernels/maxpooling_op.cc. The manipulation with an unknown input leads to a divide by zero vulnerability. The CWE definition for the vulnerability is CWE-369. The product divides a value by zero. As an impact it is known to affect availability.
The weakness was released 05/15/2021. The advisory is available at github.com. This vulnerability was named CVE-2021-29573. Successful exploitation requires user interaction by the victim. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1499 by the MITRE ATT&CK project.
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: Divide by zeroCWE: CWE-369 / CWE-404
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-29573 (🔍)
GCVE (CVE): GCVE-0-2021-29573
GCVE (VulDB): GCVE-100-175186
Entry
Created: 05/15/2021 13:44Updated: 05/19/2021 14:59
Changes: 05/15/2021 13:44 (41), 05/19/2021 14:56 (6), 05/19/2021 14:59 (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.