# GHSA-mw6j-hh29-h379: `CHECK` failure in depthwise ops via overflows > An integer overflow in TensorFlow's depthwise operations allows attackers to cause a denial of service via assertion failure. - **Severity:** Not scored - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Not stated - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 25 May 2022 ## What is GHSA-mw6j-hh29-h379? GHSA-mw6j-hh29-h379 is a vulnerability in tensorflow, published on 25 May 2022. ### Official description ### Impact The implementation of depthwise ops in TensorFlow is vulnerable to a denial of service via `CHECK`-failure (assertion failure) caused by overflowing the number of elements in a tensor: ```python import tensorflow as tf input = tf.constant(1, shape=[1, 4, 4, 3], dtype=tf.float32) filter_sizes = tf.constant(1879048192, shape=[13], dtype=tf.int32) out_backprop = tf.constant(1, shape=[1, 4, 4, 3], dtype=tf.float32) tf.raw_ops.DepthwiseConv2dNativeBackpropFilter( input=input, filter_sizes=filter_sizes, out_backprop=out_backprop, strides=[1, 1, 1, 1], padding="SAME") ``` This is another instance of [TFSA-2021-198](https://github.com/tensorflow/tensorflow/blob/master/tensorflow/security/advisory/tfsa-2021-198.md) (CVE-2021-41197). ### Patches We have patched the issue in GitHub commit [3796cc4fcd93ae55812a457abc96dcd55fbb854b](https://github.com/tensorflow/tensorflow/commit/3796cc4fcd93ae55812a457abc96dcd55fbb854b). The fix will be included in TensorFlow 2.9.0. We will also cherrypick this commit on TensorFlow 2.8.1, TensorFlow 2.7.2, and TensorFlow 2.6.4, as these are also affected and still in supported range. ### For more information Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions. ### Attribution This vulnerability has been reported by Neophytos Christou from Secure Systems Lab at Brown University. ## Which versions are affected by GHSA-mw6j-hh29-h379? 18 open source packages ship an affected version, including tensorflow, tensorflow-cpu and tensorflow-gpu. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `tensorflow` | PyPI | All versions | 2.6.4 | | `tensorflow` | PyPI | All versions | 2.6.4 | | `tensorflow` | PyPI | From 2.7.0 | 2.7.2 | | `tensorflow` | PyPI | From 2.7.0 | 2.7.2 | | `tensorflow` | PyPI | From 2.8.0 | 2.8.1 | | `tensorflow` | PyPI | From 2.8.0 | 2.8.1 | | `tensorflow-cpu` | PyPI | All versions | 2.6.4 | | `tensorflow-cpu` | PyPI | All versions | 2.6.4 | | `tensorflow-cpu` | PyPI | From 2.7.0 | 2.7.2 | | `tensorflow-cpu` | PyPI | From 2.7.0 | 2.7.2 | | `tensorflow-cpu` | PyPI | From 2.8.0 | 2.8.1 | | `tensorflow-cpu` | PyPI | From 2.8.0 | 2.8.1 | | `tensorflow-gpu` | PyPI | All versions | 2.6.4 | | `tensorflow-gpu` | PyPI | All versions | 2.6.4 | | `tensorflow-gpu` | PyPI | From 2.7.0 | 2.7.2 | | `tensorflow-gpu` | PyPI | From 2.7.0 | 2.7.2 | | `tensorflow-gpu` | PyPI | From 2.8.0 | 2.8.1 | | `tensorflow-gpu` | PyPI | From 2.8.0 | 2.8.1 | ## How do I fix GHSA-mw6j-hh29-h379? Upgrade tensorflow to a fixed version for your release line: 2.6.4, 2.7.2 or 2.8.1. ## Is GHSA-mw6j-hh29-h379 being exploited? There is no known exploitation of GHSA-mw6j-hh29-h379 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for GHSA-mw6j-hh29-h379 and fix it if it is affected. What it is: GHSA-mw6j-hh29-h379 is a vulnerability in tensorflow, published on 25 May 2022. Exploitation: There is no known exploitation of GHSA-mw6j-hh29-h379 in the wild and no public exploit code. Affected packages and fixed versions: - tensorflow (PyPI): affected all versions; fixed in 2.6.4 - tensorflow (PyPI): affected all versions; fixed in 2.6.4 - tensorflow (PyPI): affected from 2.7.0; fixed in 2.7.2 - tensorflow (PyPI): affected from 2.7.0; fixed in 2.7.2 - tensorflow (PyPI): affected from 2.8.0; fixed in 2.8.1 - tensorflow (PyPI): affected from 2.8.0; fixed in 2.8.1 - tensorflow-cpu (PyPI): affected all versions; fixed in 2.6.4 - tensorflow-cpu (PyPI): affected all versions; fixed in 2.6.4 - tensorflow-cpu (PyPI): affected from 2.7.0; fixed in 2.7.2 - tensorflow-cpu (PyPI): affected from 2.7.0; fixed in 2.7.2 - tensorflow-cpu (PyPI): affected from 2.8.0; fixed in 2.8.1 - tensorflow-cpu (PyPI): affected from 2.8.0; fixed in 2.8.1 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/GHSA-mw6j-hh29-h379/ (Markdown: https://insights.sbomify.com/GHSA-mw6j-hh29-h379/index.md) ``` ## Sources - OSV: https://osv.dev/vulnerability/GHSA-mw6j-hh29-h379 --- From sbomify Insights: https://insights.sbomify.com/GHSA-mw6j-hh29-h379/ Summaries are generated and may contain mistakes; the official description above is the record.