Google TensorFlow up to 2.10.0 pooling_ratio out-of-bounds write
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.2 | $0-$5k | 0.00 |
Summary
A vulnerability described as critical has been identified in Google TensorFlow up to 2.10.0. This issue affects some unknown processing. Such manipulation of the argument pooling_ratio leads to out-of-bounds write. This vulnerability is uniquely identified as CVE-2022-41900. The attack can be launched remotely. No exploit exists. Upgrading the affected component is recommended.
Details
A vulnerability, which was classified as critical, has been found in Google TensorFlow up to 2.10.0 (Artificial Intelligence Software). Affected by this issue is an unknown code block. The manipulation of the argument pooling_ratio with an unknown input leads to a out-of-bounds write vulnerability. Using CWE to declare the problem leads to CWE-787. The product writes data past the end, or before the beginning, of the intended buffer. Impacted is confidentiality, integrity, and availability. CVE summarizes:
TensorFlow is an open source platform for machine learning. The security vulnerability results in FractionalMax(AVG)Pool with illegal pooling_ratio. Attackers using Tensorflow can exploit the vulnerability. They can access heap memory which is not in the control of user, leading to a crash or remote code execution. We have patched the issue in GitHub commit 216525144ee7c910296f5b05d214ca1327c9ce48. The fix will be included in TensorFlow 2.11.0. We will also cherry pick this commit on TensorFlow 2.10.1.
The weakness was disclosed 11/19/2022 as GHSA-xvwp-h6jv-7472. The advisory is shared for download at github.com. This vulnerability is handled as CVE-2022-41900 since 09/30/2022. Successful exploitation requires user interaction by the victim. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 12/20/2022).
Upgrading to version 2.10.1 or 2.11.0 eliminates this vulnerability. Applying the patch 216525144ee7c910296f5b05d214ca1327c9ce48 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.
Once again VulDB remains the best source 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: 7.3VulDB Meta Temp Score: 7.2
VulDB Base Score: 5.0
VulDB Temp Score: 4.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CNA Base Score: 7.1
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: Out-of-bounds writeCWE: CWE-787 / 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.10.1/2.11.0
Patch: 216525144ee7c910296f5b05d214ca1327c9ce48
Timeline
09/30/2022 🔍11/19/2022 🔍
11/19/2022 🔍
12/20/2022 🔍
Sources
Vendor: google.comAdvisory: GHSA-xvwp-h6jv-7472
Status: Confirmed
CVE: CVE-2022-41900 (🔍)
GCVE (CVE): GCVE-0-2022-41900
GCVE (VulDB): GCVE-100-213932
Entry
Created: 11/19/2022 08:11Updated: 12/20/2022 11:32
Changes: 11/19/2022 08:11 (54), 12/20/2022 11:32 (12)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.