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.
EPSS: 0.002 (8.0th percentile) — read the EPSS interpretation.
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.
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
- security-advisories@github.com (x_refsource_CONFIRM, Exploit, Patch, Third Party Advisory)
- security-advisories@github.com (Patch, Third Party Advisory, x_refsource_MISC)
Frequently asked questions
- What is CVE-2021-41217?
- CVE-2021-41217 is a medium-severity vulnerability in Google Tensorflow, classified under NULL Pointer Dereference. CVSS score: 5.5/10. Published 2021-11-05.
- How severe is CVE-2021-41217?
- Medium severity. CVSS v3 base score is 5.5 out of 10.