Google TensorFlow up to 2.1.3/2.2.2/2.3.2/2.4.1 matrix_triangular_solve_op_impl.h MatrixTriangularSolve out-of-bounds
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.1 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Google TensorFlow up to 2.1.3/2.2.2/2.3.2/2.4.1 and classified as problematic. The impacted element is the function MatrixTriangularSolve of the file core/kernels/linalg/matrix_triangular_solve_op_impl.h. This manipulation causes out-of-bounds.
This vulnerability is handled as CVE-2021-29551. The attack can be initiated remotely. There is not any exploit available.
The affected component should be upgraded.
Details
A vulnerability has been found in Google TensorFlow up to 2.1.3/2.2.2/2.3.2/2.4.1 (Artificial Intelligence Software) and classified as problematic. Affected by this vulnerability is the function MatrixTriangularSolve of the file core/kernels/linalg/matrix_triangular_solve_op_impl.h. 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 availability.
The weakness was released 05/15/2021. It is possible to read the advisory at github.com. This vulnerability is known as CVE-2021-29551. It demands that the victim is doing some kind of user interaction. Technical details of the vulnerability 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.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
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-29551 (🔍)
GCVE (CVE): GCVE-0-2021-29551
GCVE (VulDB): GCVE-100-175171
Entry
Created: 05/15/2021 11:22Updated: 05/19/2021 13:06
Changes: 05/15/2021 11:22 (41), 05/19/2021 12:59 (6), 05/19/2021 13:06 (1)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.