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, the implementation of `tf.raw_ops.UnsortedSegmentJoin` does not fully validate the input arguments. This results in a `CHECK`-failure which can be used to trigger a denial of service attack. The code assumes `num_segments` is a scalar but there is no validation for this before accessing its value. 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 | |
Google TensorFlow | =2.7.0-rc0 | |
Google TensorFlow | =2.7.0-rc1 | |
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-29197 has a high severity rating due to the potential for denial of service attacks.
To fix CVE-2022-29197, upgrade TensorFlow to versions 2.9.0, 2.8.1, 2.7.2, or 2.6.4 or later.
CVE-2022-29197 affects all TensorFlow versions prior to 2.9.0, 2.8.1, 2.7.2, and 2.6.4.
The vulnerability in CVE-2022-29197 exists in the `tf.raw_ops.UnsortedSegmentJoin` implementation.
CVE-2022-29197 can be exploited to trigger a denial of service through a CHECK-failure.