CVE-2020-5215
What it 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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account, but needs a user to act. Limited direct impact.
- Exploit odds
- 0.6% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.6% in the next 30 days (EPSS).
- Severity: 5.0 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.6% · EPSS, next 30 days
- Weakness
- CWE-754
- Record status
- Modified
Affected
- Google Tensorflow < 1.15.2
- Google Tensorflow < 2.0.1
Attack profile CVSS 3.1 · 5.0
- Attack vector
- Local
- Complexity
- High
- Privileges needed
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
Raw vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:L
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2020-5215.md and follow it. Check whether this project is affected by CVE-2020-5215. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://github.com/tensorflow/tensorflow/commit/5ac1b9e24ff6afc465756edf845d2e9660bd34bf
- https://github.com/tensorflow/tensorflow/releases/tag/v1.15.2
- https://github.com/tensorflow/tensorflow/releases/tag/v2.0.1
- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-977j-xj7q-2jr9
- https://github.com/tensorflow/tensorflow/commit/5ac1b9e24ff6afc465756edf845d2e9660bd34bf
- https://github.com/tensorflow/tensorflow/releases/tag/v1.15.2
- https://github.com/tensorflow/tensorflow/releases/tag/v2.0.1
- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-977j-xj7q-2jr9
References
- https://github.com/tensorflow/tensorflow/commit/5ac1b9e24ff6afc465756edf845d2e9660bd34bf
- https://github.com/tensorflow/tensorflow/releases/tag/v1.15.2
- https://github.com/tensorflow/tensorflow/releases/tag/v2.0.1
- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-977j-xj7q-2jr9
- https://github.com/tensorflow/tensorflow/commit/5ac1b9e24ff6afc465756edf845d2e9660bd34bf
- https://github.com/tensorflow/tensorflow/releases/tag/v1.15.2
- https://github.com/tensorflow/tensorflow/releases/tag/v2.0.1
- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-977j-xj7q-2jr9