Arbitrary memory read in `ImmutableConst`
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 affected versions the `ImmutableConst` operation in TensorFlow can be tricked into reading arbitrary memory contents. This is because the `tstring` TensorFlow string class has a special case for memory mapped strings but the operation itself does not offer any support for this datatype. 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 packages, the ImmutableConst operation does not support memory-mapped strings and can be tricked into reading arbitrary memory contents. The input does not specify whether exploitation requires network or local access, authentication, or user interaction.
Users of the PyPI tensorflow, tensorflow-cpu, or tensorflow-gpu packages should check versions before 2.4.4, 2.5.0 through 2.5.1, 2.6.0, and 2.7.0 release candidates.