| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.2 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in TensorFlow up to 1.15.4/2.0.3/2.1.2/2.2.1/2.3.1. The impacted element is an unknown function of the component LSTM/GRU. This manipulation causes denial of service. This vulnerability is tracked as CVE-2020-26270. The attack is restricted to local execution. No exploit exists. It is recommended to upgrade the affected component.
Details
A vulnerability classified as problematic was found in TensorFlow up to 1.15.4/2.0.3/2.1.2/2.2.1/2.3.1 (Artificial Intelligence Software). Affected by this vulnerability is some unknown processing of the component LSTM/GRU. The manipulation with an unknown input leads to a denial of service vulnerability. The CWE definition for the vulnerability is CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. As an impact it is known to affect availability.
The weakness was disclosed 12/11/2020. The advisory is shared at github.com. This vulnerability is known as CVE-2020-26270. 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.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
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-26270 (🔍)
GCVE (CVE): GCVE-0-2020-26270
GCVE (VulDB): GCVE-100-165997
Entry
Created: 12/11/2020 08:29Updated: 12/15/2020 18:29
Changes: 12/11/2020 08:29 (39), 12/15/2020 18:22 (6), 12/15/2020 18:29 (1)
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.