Google TensorFlow up to 2.7.1/2.8.0/2.9.0 FractionalMaxPoolGrad assertion
| 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 impacts the function FractionalMaxPoolGrad. This manipulation causes assertion.
This vulnerability is handled as CVE-2022-35981. The attack can be initiated remotely. There is not any exploit available.
It is recommended to upgrade the affected component.
Details
A vulnerability has been found in Google TensorFlow up to 2.7.1/2.8.0/2.9.0 (Artificial Intelligence Software) and classified as problematic. Affected by this vulnerability is the function FractionalMaxPoolGrad. The manipulation with an unknown input leads to a assertion vulnerability. The CWE definition for the vulnerability is CWE-617. The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary. As an impact it is known to affect availability. The summary by CVE is:
TensorFlow is an open source platform for machine learning. `FractionalMaxPoolGrad` validates its inputs with `CHECK` failures instead of with returning errors. If it gets incorrectly sized inputs, the `CHECK` failure can be used to trigger a denial of service attack. We have patched the issue in GitHub commit 8741e57d163a079db05a7107a7609af70931def4. 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 released 09/17/2022 as GHSA-vxv8-r8q2-63xw. The advisory is shared at github.com. This vulnerability is known as CVE-2022-35981 since 07/15/2022. Technical details are known, but no exploit is available.
Upgrading to version 2.7.2, 2.8.1, 2.9.1 or 2.10.0 eliminates this vulnerability. Applying the patch 8741e57d163a079db05a7107a7609af70931def4 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.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: AssertionCWE: CWE-617
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: 8741e57d163a079db05a7107a7609af70931def4
Timeline
07/15/2022 🔍09/17/2022 🔍
09/17/2022 🔍
10/19/2022 🔍
Sources
Vendor: google.comAdvisory: GHSA-vxv8-r8q2-63xw
Status: Confirmed
CVE: CVE-2022-35981 (🔍)
GCVE (CVE): GCVE-0-2022-35981
GCVE (VulDB): GCVE-100-208921
Entry
Created: 09/17/2022 08:45Updated: 10/19/2022 17:14
Changes: 09/17/2022 08:45 (54), 10/19/2022 17:14 (11)
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.