// For flags

CVE-2020-5215

Segmentation faultin TensorFlow when converting a Python string to tf.float16

Severity Score

7.5
*CVSS v3.1

Exploit Likelihood

*EPSS

Affected Versions

*CPE

Public Exploits

1
*Multiple Sources

Exploited in Wild

-
*KEV

Decision

-
*SSVC
Descriptions

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.

En TensorFlow versiones anteriores a 1.15.2 y 2.0.1, la conversión de una cadena (de Python) a un valor tf.float16 resulta en un fallo de segmentación en modo eager, ya que las comprobaciones de formato para este caso de uso solo están en el modo graph. Este problema puede conllevar a una denegación de servicio en inference/training, donde un atacante malicioso puede enviar un punto de datos que contiene una cadena en lugar de un valor tf.float16. Efectos similares pueden ser obtenidos mediante la manipulación de modelos guardados y puntos de control por los cuales se reemplaza un valor escalar tf.float16 por una cadena escalar, este problema se desencadenará debido a las conversiones automáticas. Esto puede ser reproducido fácilmente mediante tf.constant("hello", tf.float16), si una ejecución eager es habilitada. Este problema es parcheado en TensorFlow versiones 1.15.1 y 2.0.1 con esta vulnerabilidad parcheada. TensorFlow versión 2.1.0 fue publicada después de que corregimos el problema, por lo que no está afectado. Se incentiva a los usuarios a cambiar a TensorFlow versiones 1.15.1, 2.0.1 o 2.1.0.

*Credits: N/A
CVSS Scores
Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High
Attack Vector
Local
Attack Complexity
High
Privileges Required
Low
User Interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low
Attack Vector
Network
Attack Complexity
Medium
Authentication
None
Confidentiality
None
Integrity
None
Availability
Partial
* Common Vulnerability Scoring System
SSVC
  • Decision:-
Exploitation
-
Automatable
-
Tech. Impact
-
* Organization's Worst-case Scenario
Timeline
  • 2020-01-02 CVE Reserved
  • 2020-01-28 CVE Published
  • 2024-06-10 EPSS Updated
  • 2024-08-04 CVE Updated
  • 2024-08-04 First Exploit
  • ---------- Exploited in Wild
  • ---------- KEV Due Date
CWE
  • CWE-20: Improper Input Validation
  • CWE-754: Improper Check for Unusual or Exceptional Conditions
CAPEC
Affected Vendors, Products, and Versions
Vendor Product Version Other Status
Vendor Product Version Other Status <-- --> Vendor Product Version Other Status
Google
Search vendor "Google"
 Tensorflow
Search vendor "Google" for product "Tensorflow"
 < 1.15.2
Search vendor "Google" for product "Tensorflow" and version " < 1.15.2"
-
Affected
Google
Search vendor "Google"
 Tensorflow
Search vendor "Google" for product "Tensorflow"
 >= 2.0.0 < 2.0.1
Search vendor "Google" for product "Tensorflow" and version " >= 2.0.0 < 2.0.1"
-
Affected