Improper input validation in Google Tensorflow
CVE-2022-35986
TensorFlow is an open source platform for machine learning. If `RaggedBincount` is given an empty input tensor `splits`, it results in a segfault that can be used to trigger a denial of service attack. We have patched the issue in GitHub commit 7a4591fd4f065f4fa903593bc39b2f79530a74b8. 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.
Vulnerability class: Drupalgeddon 2 (CVE-2018-7600)
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, 44.8th 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 2 other repositories (gclonly/im, iotdscreator/iotdscreator-dataset). 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-wr9v-g9vf-c74v (Third Party Advisory)
- github.com/tensorflow/tensorflow/commit/7a4591fd4f065f4fa903593bc39b2f79530a74b8 (Patch, Third Party Advisory)