Segfault in `RaggedBincount` in TensorFlow
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.7.2, 2.8.1, 2.9.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- tensorflow tensorflow
fixed in 2.7.2; From 2.8.0 · fixed in 2.8.1; From 2.9.0 · fixed in 2.9.1
- tensorflowPyPI
fixed in 2.7.2
- tensorflowPyPI
From 2.8.0 · fixed in 2.8.1
- tensorflowPyPI
From 2.9.0 · fixed in 2.9.1
- tensorflowPyPI
fixed in 2.7.2; From 2.8.0 · fixed in 2.8.1; From 2.9.0 · fixed in 2.9.1