Google TensorFlow up to 2.8.3/2.9.2/2.10.0 tf.raw_ops.ImageProjectiveTransformV2 buffer size
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in Google TensorFlow up to 2.8.3/2.9.2/2.10.0. Affected is the function tf.raw_ops.ImageProjectiveTransformV2. This manipulation causes buffer size.
The identification of this vulnerability is CVE-2022-41886. It is possible to initiate the attack remotely. There is no exploit available.
It is advisable to upgrade the affected component.
Details
A vulnerability classified as problematic was found in Google TensorFlow up to 2.8.3/2.9.2/2.10.0 (Artificial Intelligence Software). Affected by this vulnerability is the function tf.raw_ops.ImageProjectiveTransformV2. The manipulation with an unknown input leads to a buffer size vulnerability. The CWE definition for the vulnerability is CWE-131. The product does not correctly calculate the size to be used when allocating a buffer, which could lead to a buffer overflow. As an impact it is known to affect availability. The summary by CVE is:
TensorFlow is an open source platform for machine learning. When `tf.raw_ops.ImageProjectiveTransformV2` is given a large output shape, it overflows. We have patched the issue in GitHub commit 8faa6ea692985dbe6ce10e1a3168e0bd60a723ba. The fix will be included in TensorFlow 2.11. We will also cherrypick this commit on TensorFlow 2.10.1, 2.9.3, and TensorFlow 2.8.4, as these are also affected and still in supported range.
The weakness was shared 11/19/2022 as GHSA-54pp-c6pp-7fpx. The advisory is shared at github.com. This vulnerability is known as CVE-2022-41886 since 09/30/2022. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.
Upgrading to version 2.8.4, 2.9.3, 2.10.1 or 2.11 eliminates this vulnerability. Applying the patch 8faa6ea692985dbe6ce10e1a3168e0bd60a723ba 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 the best quality for vulnerability data then you always have to consider 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: 5.1VulDB Meta Temp Score: 5.1
VulDB Base Score: 3.1
VulDB Temp Score: 3.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CNA Base Score: 4.8
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: Buffer sizeCWE: CWE-131 / CWE-120 / 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.8.4/2.9.3/2.10.1/2.11
Patch: 8faa6ea692985dbe6ce10e1a3168e0bd60a723ba
Timeline
09/30/2022 🔍11/19/2022 🔍
11/19/2022 🔍
12/20/2022 🔍
Sources
Vendor: google.comAdvisory: GHSA-54pp-c6pp-7fpx
Status: Confirmed
CVE: CVE-2022-41886 (🔍)
GCVE (CVE): GCVE-0-2022-41886
GCVE (VulDB): GCVE-100-213949
Entry
Created: 11/19/2022 08:29Updated: 12/20/2022 13:16
Changes: 11/19/2022 08:29 (53), 12/20/2022 13:16 (12)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.