CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
4.1 | $0-$5k | 0.00 |
A vulnerability, which was classified as problematic, has been found in TensorFlow up to 1.15.1/2.0.0. This issue affects some unknown functionality of the component Eager Mode. The manipulation as part of a String leads to a unusual condition vulnerability. Using CWE to declare the problem leads to CWE-754. The product does not check or incorrectly checks for unusual or exceptional conditions that are not expected to occur frequently during day to day operation of the product. Impacted is availability. The summary by CVE is:
In TensorFlow before 1.15.2 and 2.0.1, converting a string (from Python) to a tf.float16 value results in a segmentation fault in eager mode as the format checks for this use case are only in the graph mode. This issue can lead to denial of service in inference/training where a malicious attacker can send a data point which contains a string instead of a tf.float16 value. Similar effects can be obtained by manipulating saved models and checkpoints whereby replacing a scalar tf.float16 value with a scalar string will trigger this issue due to automatic conversions. This can be easily reproduced by tf.constant("hello", tf.float16), if eager execution is enabled. This issue is patched in TensorFlow 1.15.1 and 2.0.1 with this vulnerability patched. TensorFlow 2.1.0 was released after we fixed the issue, thus it is not affected. Users are encouraged to switch to TensorFlow 1.15.1, 2.0.1 or 2.1.0.
The weakness was released 01/28/2020 (GitHub Repository). The advisory is shared at github.com. The identification of this vulnerability is CVE-2020-5215 since 01/02/2020. The exploitation is known to be difficult. An attack has to be approached locally. A simple authentication is required for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.
Upgrading to version 1.15.1, 2.0.1 or 2.1.0 eliminates this vulnerability.
Entries connected to this vulnerability are available at VDB-223853, VDB-223854, VDB-223855 and VDB-223856.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB CVSS-B Score: 🔍VulDB CVSS-BT Score: 🔍
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.2VulDB Meta Temp Score: 4.1
VulDB Base Score: 2.5
VulDB Temp Score: 2.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.0
NVD Vector: 🔍
CNA Base Score: 5.0
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Unusual conditionCWE: CWE-754
CAPEC: 🔍
ATT&CK: 🔍
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.1/2.0.1/2.1.0
Patch: github.com
Timeline
01/02/2020 🔍01/28/2020 🔍
01/29/2020 🔍
03/27/2024 🔍
Sources
Advisory: 5ac1b9e24ff6afc465756edf845d2e9660bd34bfStatus: Not defined
CVE: CVE-2020-5215 (🔍)
See also: 🔍
Entry
Created: 01/29/2020 06:54Updated: 03/27/2024 11:56
Changes: 01/29/2020 06:54 (39), 01/29/2020 06:59 (11), 03/27/2024 11:48 (20), 03/27/2024 11:56 (19)
Complete: 🔍
Cache ID: 18:DEF:103
No comments yet. Languages: en.
Please log in to comment.