Skip to content

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

High severity GitHub Reviewed Published Jan 28, 2020 in tensorflow/tensorflow • Updated Jan 9, 2023

Package

pip tensorflow (pip)

Affected versions

< 1.15.2
= 2.0.0

Patched versions

1.15.2
2.0.1
pip tensorflow-cpu (pip)
< 1.15.2
= 2.0.0
1.15.2
2.0.1
pip tensorflow-gpu (pip)
< 1.15.2
= 2.0.0
1.15.2
2.0.1

Description

Impact

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.

Patches

We have patched the vulnerability in GitHub commit 5ac1b9.

We are additionally releasing 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.

We encourage users to switch to TensorFlow 1.15.1, 2.0.1 or 2.1.0.

For more information

Please consult SECURITY.md for more information regarding the security model and how to contact us with issues and questions.

References

@mihaimaruseac mihaimaruseac published to tensorflow/tensorflow Jan 28, 2020
Reviewed Jan 28, 2020
Published to the GitHub Advisory Database Jan 28, 2020
Last updated Jan 9, 2023

Severity

High

Weaknesses

CVE ID

CVE-2020-5215

GHSA ID

GHSA-977j-xj7q-2jr9

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.