PYSEC-2020-305

See a problem?
Import Source
https://github.com/pypa/advisory-database/blob/main/vulns/tensorflow-gpu/PYSEC-2020-305.yaml
JSON Data
https://api.osv.dev/v1/vulns/PYSEC-2020-305
Aliases
Published
2020-09-25T19:15:00Z
Modified
2023-12-06T01:00:16.028491Z
Summary
[none]
Details

In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the tf.raw_ops.Switch operation takes as input a tensor and a boolean and outputs two tensors. Depending on the boolean value, one of the tensors is exactly the input tensor whereas the other one should be an empty tensor. However, the eager runtime traverses all tensors in the output. Since only one of the tensors is defined, the other one is nullptr, hence we are binding a reference to nullptr. This is undefined behavior and reported as an error if compiling with -fsanitize=null. In this case, this results in a segmentation fault The issue is patched in commit da8558533d925694483d2c136a9220d6d49d843c, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.

References

Affected packages

PyPI / tensorflow-gpu

Package

Affected ranges

Type
GIT
Repo
https://github.com/tensorflow/tensorflow
Events
Introduced
0 Unknown introduced commit / All previous commits are affected
Fixed
Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
1.15.4
Introduced
2.0.0
Fixed
2.0.3
Introduced
2.1.0
Fixed
2.1.2
Introduced
2.2.0
Fixed
2.2.1
Introduced
2.3.0
Fixed
2.3.1

Affected versions

0.*

0.12.0
0.12.1

1.*

1.0.0
1.0.1
1.1.0
1.2.0
1.2.1
1.3.0
1.4.0
1.4.1
1.5.0
1.5.1
1.6.0
1.7.0
1.7.1
1.8.0
1.9.0
1.10.0
1.10.1
1.11.0
1.12.0
1.12.2
1.12.3
1.13.1
1.13.2
1.14.0
1.15.0
1.15.2
1.15.3

2.*

2.0.0
2.0.1
2.0.2
2.1.0
2.1.1
2.2.0
2.3.0