| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in TensorFlow up to 1.15.4/2.0.3/2.1.2/2.2.1/2.3.1. This vulnerability affects unknown code of the component Model Handler. Performing a manipulation results in uninitialized resource. This vulnerability was named CVE-2020-26266. The attack needs to be approached locally. There is no available exploit. You should 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 classified as problematic. This affects some unknown functionality of the component Model Handler. The manipulation with an unknown input leads to a uninitialized resource vulnerability. CWE is classifying the issue as CWE-908. The product uses or accesses a resource that has not been initialized. This is going to have an impact on confidentiality, integrity, and availability.
The weakness was presented 12/11/2020. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2020-26266. Neither technical details nor an exploit are publicly available.
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.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
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: Uninitialized resourceCWE: CWE-908
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-26266 (🔍)
GCVE (CVE): GCVE-0-2020-26266
GCVE (VulDB): GCVE-100-165993
Entry
Created: 12/11/2020 08:24Updated: 12/15/2020 17:55
Changes: 12/11/2020 08:24 (38), 12/15/2020 17:50 (6), 12/15/2020 17:55 (1)
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.