Unitialized access in `EinsumHelper::ParseEquation`
tensorflow
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
tensorflow
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
| tensorflow-cpu PyPI |
|
|
| tensorflow-gpu PyPI |
|
|
TensorFlow is an open source platform for machine learning. In affeced versions during execution, `EinsumHelper::ParseEquation()` is supposed to set the flags in `input_has_ellipsis` vector and `*output_has_ellipsis` boolean to indicate whether there is ellipsis in the corresponding inputs and output. However, the code only changes these flags to `true` and never assigns `false`. This results in unitialized variable access if callers assume that `EinsumHelper::ParseEquation()` always sets these flags. 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.
From the CVE record · GitHub_M
In affected TensorFlow versions, EinsumHelper::ParseEquation() does not set ellipsis flags to false, which can lead to uninitialized variable access during execution. The input does not specify an attacker action or whether exploitation requires network access, authentication, or user interaction.
Anyone using the PyPI tensorflow, tensorflow-cpu, or tensorflow-gpu packages should check versions earlier than 2.4.4, 2.5.0 through 2.5.1, 2.6.0, and 2.7.0 release candidates.