TensorFlow up to 2.3.1 Python Interpreter tf.raw_ops.ImmutableConst denial of service
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.2 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in TensorFlow up to 1.15.4/2.0.3/2.1.2/2.2.1/2.3.1. Impacted is the function tf.raw_ops.ImmutableConst of the component Python Interpreter. The manipulation leads to denial of service.
This vulnerability is referenced as CVE-2020-26268. The attack can only be performed from a local environment. No exploit is available.
It is suggested to upgrade the affected component.
Details
A vulnerability was found in TensorFlow up to 1.15.4/2.0.3/2.1.2/2.2.1/2.3.1 (Artificial Intelligence Software). It has been rated as problematic. This issue affects the function tf.raw_ops.ImmutableConst of the component Python Interpreter. The manipulation with an unknown input leads to a denial of service vulnerability. Using CWE to declare the problem leads to CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. Impacted is availability.
The weakness was published 12/11/2020. It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2020-26268. Technical details of the vulnerability are known, but there is no available exploit.
Upgrading to version 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2 or 2.4.0 eliminates this vulnerability. Applying a patch 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.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.3VulDB Meta Temp Score: 3.2
VulDB Base Score: 3.3
VulDB Temp Score: 3.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: Denial of serviceCWE: CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
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 1.15.5/2.0.4/2.1.3/2.2.2/2.3.2/2.4.0
Patch: github.com
Timeline
10/01/2020 🔍12/11/2020 🔍
12/11/2020 🔍
12/15/2020 🔍
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2020-26268 (🔍)
GCVE (CVE): GCVE-0-2020-26268
GCVE (VulDB): GCVE-100-165995
Entry
Created: 12/11/2020 08:26Updated: 12/15/2020 18:12
Changes: 12/11/2020 08:26 (40), 12/15/2020 18:07 (6), 12/15/2020 18:12 (1)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.