Google TensorFlow up to 2.11.0 tf.raw_ops.Bincount weights comparison
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.8 | $0-$5k | 0.00 |
Summary
A vulnerability described as problematic has been identified in Google TensorFlow up to 2.11.0. This affects the function tf.raw_ops.Bincount. Executing a manipulation of the argument weights can lead to comparison.
This vulnerability appears as CVE-2023-25675. The attack may be performed from remote. There is no available exploit.
Upgrading the affected component is recommended.
Details
A vulnerability classified as problematic was found in Google TensorFlow up to 2.11.0 (Artificial Intelligence Software). This vulnerability affects the function tf.raw_ops.Bincount. The manipulation of the argument weights with an unknown input leads to a comparison vulnerability. The CWE definition for the vulnerability is CWE-697. The product compares two entities in a security-relevant context, but the comparison is incorrect, which may lead to resultant weaknesses. As an impact it is known to affect availability. CVE summarizes:
TensorFlow is an open source machine learning platform. When running versions prior to 2.12.0 and 2.11.1 with XLA, `tf.raw_ops.Bincount` segfaults when given a parameter `weights` that is neither the same shape as parameter `arr` nor a length-0 tensor. A fix is included in TensorFlow 2.12.0 and 2.11.1.
The weakness was presented 03/25/2023 as GHSA-7x4v-9gxg-9hwj. The advisory is available at github.com. This vulnerability was named CVE-2023-25675 since 02/09/2023. Successful exploitation requires user interaction by the victim. Technical details are known, but there is no available exploit.
Upgrading to version 2.11.1 or 2.12.0 eliminates this vulnerability. Applying the patch 8ae76cf085f4be26295d2ecf2081e759e04b8acf 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: 5.9VulDB Meta Temp Score: 5.8
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 7.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: ComparisonCWE: CWE-697
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.11.1/2.12.0
Patch: 8ae76cf085f4be26295d2ecf2081e759e04b8acf
Timeline
02/09/2023 🔍03/25/2023 🔍
03/25/2023 🔍
03/25/2023 🔍
Sources
Vendor: google.comAdvisory: GHSA-7x4v-9gxg-9hwj
Status: Confirmed
CVE: CVE-2023-25675 (🔍)
GCVE (CVE): GCVE-0-2023-25675
GCVE (VulDB): GCVE-100-223858
Entry
Created: 03/25/2023 07:58Changes: 03/25/2023 07:58 (54)
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.