NULL pointer dereference in Google Tensorflow
CVE-2021-41217
TensorFlow is an open source platform for machine learning. In affected versions the process of building the control flow graph for a TensorFlow model is vulnerable to a null pointer exception when nodes that should be paired are not. This occurs because the code assumes that the first node in the pairing (e.g., an `Enter` node) always exists when encountering the second node (e.g., an `Exit` node). When this is not the case, `parent` is `nullptr` so dereferencing it causes a crash. The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 5.5 (Medium). Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.
EPSS exploit prediction
EPSS 0.002, 8.4th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Google Tensorflow — versions 2.6.0
- Tensorflow — versions >= 2.6.0, < 2.6.1, >= 2.5.0, < 2.5.2, < 2.4.4
Weakness classification (CWE)
References
- github.com/tensorflow/tensorflow/security/advisories/GHSA-5crj-c72x-m7gq (Exploit, Patch, Third Party Advisory)
- github.com/tensorflow/tensorflow/commit/05cbebd3c6bb8f517a158b0155debb8df79017ff (Patch, Third Party Advisory)