First published: Fri May 20 2022(Updated: )
TensorFlow is an open source platform for machine learning. Prior to versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4, multiple TensorFlow operations misbehave in eager mode when the resource handle provided to them is invalid. In graph mode, it would have been impossible to perform these API calls, but migration to TF 2.x eager mode opened up this vulnerability. If the resource handle is empty, then a reference is bound to a null pointer inside TensorFlow codebase (various codepaths). This is undefined behavior. Versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4 contain a patch for this issue.
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Google TensorFlow | <2.6.4 | |
Google TensorFlow | >=2.7.0<2.7.2 | |
Google TensorFlow | =2.7.0-rc0 | |
Google TensorFlow | =2.7.0-rc1 | |
Google TensorFlow | =2.8.0 | |
Google TensorFlow | =2.8.0-rc0 | |
Google TensorFlow | =2.8.0-rc1 | |
Google TensorFlow | =2.9.0-rc0 | |
Google TensorFlow | =2.9.0-rc1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2022-29207 is considered a medium severity vulnerability affecting TensorFlow operations due to improper handling of invalid resource handles.
To fix CVE-2022-29207, upgrade to TensorFlow versions 2.6.4, 2.7.2, 2.8.1, or 2.9.0 or later.
CVE-2022-29207 affects TensorFlow versions prior to 2.6.4, including versions 2.6.0 to 2.8.0.
CVE-2022-29207 may lead to unexpected behavior or crashes in applications utilizing TensorFlow.
No, CVE-2022-29207 is not classified as a critical vulnerability, but it still poses potential risks if left unaddressed.