CVE-2020-5215
Description
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.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
OS impact
Debian Fixed 2 releases
| Version | Status | Fixed in |
|---|---|---|
| sid | Fixed | 0 |
| forky | Fixed | 0 |
Package impact
| Ecosystem | Package | Vulnerable | Fixed |
|---|---|---|---|
| PyPI | tensorflow | <1.15.2 | 1.15.2 |
| PyPI | tensorflow | >=2.0.0,<2.0.1 | 2.0.1 |
| PyPI | tensorflow-cpu | <1.15.2 | 1.15.2 |
| PyPI | tensorflow-cpu | >=2.0.0,<2.0.1 | 2.0.1 |
| PyPI | tensorflow-gpu | <1.15.2 | 1.15.2 |
| PyPI | tensorflow-gpu | >=2.0.0,<2.0.1 | 2.0.1 |
| PyPI | tensorflow-gpu | <5ac1b9e24ff6afc465756edf845d2e9660bd34bf||>=2.0.0,<2.0.1 | 5ac1b9e24ff6afc465756edf845d2e9660bd34bf |
| PyPI | tensorflow | <5ac1b9e24ff6afc465756edf845d2e9660bd34bf||>=2.0.0,<2.0.1 | 5ac1b9e24ff6afc465756edf845d2e9660bd34bf |
| PyPI | tensorflow-cpu | <5ac1b9e24ff6afc465756edf845d2e9660bd34bf||>=2.0.0,<2.0.1 | 5ac1b9e24ff6afc465756edf845d2e9660bd34bf |
References
- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-977j-xj7q-2jr9
- https://nvd.nist.gov/vuln/detail/CVE-2020-5215
- https://github.com/tensorflow/tensorflow/commit/5ac1b9e24ff6afc465756edf845d2e9660bd34bf
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2020-303.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2020-338.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2020-258.yaml
- https://github.com/tensorflow/tensorflow
- https://github.com/tensorflow/tensorflow/releases/tag/v1.15.2
- https://github.com/tensorflow/tensorflow/releases/tag/v2.0.1
- https://security-tracker.debian.org/tracker/CVE-2020-5215
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.