Google TensorFlow up to 2.7.1/2.8.0/2.9.0 QuantizedMatMul min_a/max_a/min_b/max_b denial of service
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.7 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in Google TensorFlow up to 2.7.1/2.8.0/2.9.0. This vulnerability affects the function QuantizedMatMul. Performing a manipulation of the argument min_a/max_a/min_b/max_b results in denial of service.
This vulnerability was named CVE-2022-35973. The attack may be initiated remotely. There is no available exploit.
It is recommended to upgrade the affected component.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Details
A vulnerability, which was classified as problematic, was found in Google TensorFlow up to 2.7.1/2.8.0/2.9.0 (Artificial Intelligence Software). This affects the function QuantizedMatMul. The manipulation of the argument min_a/max_a/min_b/max_b with an unknown input leads to a denial of service vulnerability. CWE is classifying the issue as CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. This is going to have an impact on availability. The summary by CVE is:
TensorFlow is an open source platform for machine learning. If `QuantizedMatMul` is given nonscalar input for: `min_a`, `max_a`, `min_b`, or `max_b` It gives a segfault that can be used to trigger a denial of service attack. We have patched the issue in GitHub commit aca766ac7693bf29ed0df55ad6bfcc78f35e7f48. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue.
The weakness was presented 09/17/2022 as GHSA-689c-r7h2-fv9v. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2022-35973 since 07/15/2022. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1499 for this issue.
Upgrading to version 2.7.2, 2.8.1, 2.9.1 or 2.10.0 eliminates this vulnerability. Applying the patch aca766ac7693bf29ed0df55ad6bfcc78f35e7f48 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: 5.7VulDB Meta Temp Score: 5.7
VulDB Base Score: 3.7
VulDB Temp Score: 3.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CNA Base Score: 5.9
CNA Vector (GitHub, Inc.): 🔍
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: Denial of serviceCWE: 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.7.2/2.8.1/2.9.1/2.10.0
Patch: aca766ac7693bf29ed0df55ad6bfcc78f35e7f48
Timeline
07/15/2022 🔍09/17/2022 🔍
09/17/2022 🔍
10/19/2022 🔍
Sources
Vendor: google.comAdvisory: GHSA-689c-r7h2-fv9v
Status: Confirmed
CVE: CVE-2022-35973 (🔍)
GCVE (CVE): GCVE-0-2022-35973
GCVE (VulDB): GCVE-100-208893
Entry
Created: 09/17/2022 08:13 AMUpdated: 10/19/2022 02:47 PM
Changes: 09/17/2022 08:13 AM (55), 10/19/2022 02:47 PM (11)
Complete: 🔍
Cache ID: 244:E4A:40
No comments yet. Languages: en.
Please log in to comment.