Google Tensorflow up to 2.5.2/2.6.2/2.7.0 resource consumption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in Google Tensorflow up to 2.5.2/2.6.2/2.7.0. This issue affects some unknown processing. This manipulation causes resource consumption. This vulnerability is handled as CVE-2022-23580. The attack can be initiated remotely. There is not any exploit available. It is advisable to upgrade the affected component.
Details
A vulnerability has been found in Google Tensorflow up to 2.5.2/2.6.2/2.7.0 (Artificial Intelligence Software) and classified as problematic. Affected by this vulnerability is an unknown functionality. The manipulation with an unknown input leads to a resource consumption vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect availability.
The weakness was released 02/05/2022 as GHSA-627q-g293-49q7. The advisory is shared at github.com. This vulnerability is known as CVE-2022-23580 since 01/19/2022. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1499 for this issue.
Upgrading to version 2.5.3, 2.6.3, 2.7.1 or 2.8.0 eliminates this vulnerability. Applying the patch 1361fb7e29449629e1df94d44e0427ebec8c83c7 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.
Several companies clearly confirm that VulDB is the primary source for best 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.4VulDB Meta Temp Score: 5.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 6.5
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: 1361fb7e29449629e1df94d44e0427ebec8c83c7
Timeline
01/19/2022 🔍02/05/2022 🔍
02/05/2022 🔍
02/07/2022 🔍
Sources
Vendor: google.comAdvisory: GHSA-627q-g293-49q7
Status: Confirmed
CVE: CVE-2022-23580 (🔍)
GCVE (CVE): GCVE-0-2022-23580
GCVE (VulDB): GCVE-100-192361
Entry
Created: 02/05/2022 08:46Updated: 02/07/2022 12:53
Changes: 02/05/2022 08:46 (52), 02/07/2022 12:53 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.