NULL pointer dereference in Google Tensorflow
CVE-2022-35965
TensorFlow is an open source platform for machine learning. If `LowerBound` or `UpperBound` is given an empty`sorted_inputs` input, it results in a `nullptr` dereference, leading to a segfault that can be used to trigger a denial of service attack. We have patched the issue in GitHub commit bce3717eaef4f769019fd18e990464ca4a2efeea. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 5.9 (Medium). Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H.
EPSS exploit prediction
EPSS 0.005, 41.3th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Google Tensorflow — versions 2.10
- Tensorflow — versions < 2.7.2, >= 2.8.0, < 2.8.1, >= 2.9.0, < 2.9.1
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 1 other repository (gclonly/im). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- github.com/tensorflow/tensorflow/security/advisories/GHSA-qxpx-j395-pw36 (Patch, Third Party Advisory)
- github.com/tensorflow/tensorflow/commit/bce3717eaef4f769019fd18e990464ca4a2efeea (Patch, Third Party Advisory)