Google Tensorflow up to 2.5.2/2.6.2/2.7.0 ThreadPoolHandle num_threads resource consumption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Google Tensorflow up to 2.5.2/2.6.2/2.7.0. It has been declared as problematic. Affected by this vulnerability is the function ThreadPoolHandle. Such manipulation of the argument num_threads leads to resource consumption.
This vulnerability is referenced as CVE-2022-21732. It is possible to launch the attack remotely. No exploit is available.
It is recommended to upgrade the affected component.
Details
A vulnerability, which was classified as problematic, has been found in Google Tensorflow up to 2.5.2/2.6.2/2.7.0 (Artificial Intelligence Software). Affected by this issue is the function ThreadPoolHandle. The manipulation of the argument num_threads with an unknown input leads to a resource consumption vulnerability. Using CWE to declare the problem leads to CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. Impacted is availability.
The weakness was published 02/03/2022 as GHSA-c582-c96p-r5cq. The advisory is available at github.com. This vulnerability is handled as CVE-2022-21732 since 11/16/2021. 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.5.3, 2.6.3, 2.7.1 or 2.8.0 eliminates this vulnerability. Applying the patch e3749a6d5d1e8d11806d4a2e9cc3123d1a90b75e 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.2
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 4.3
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: Resource consumptionCWE: CWE-400 / 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.5.3/2.6.3/2.7.1/2.8.0
Patch: e3749a6d5d1e8d11806d4a2e9cc3123d1a90b75e
Timeline
11/16/2021 🔍02/03/2022 🔍
02/03/2022 🔍
02/05/2022 🔍
Sources
Vendor: google.comAdvisory: GHSA-c582-c96p-r5cq
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2022-21732 (🔍)
GCVE (CVE): GCVE-0-2022-21732
GCVE (VulDB): GCVE-100-192170
Entry
Created: 02/03/2022 15:07Updated: 02/05/2022 08:26
Changes: 02/03/2022 15:07 (54), 02/05/2022 08:26 (2)
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.