# GHSA-cqvq-fvhr-v6hc: `CHECK` failure in `SobolSample` via missing validation > A missing validation in TensorFlow's SobolSample operation allows attackers to cause a denial of service via crafted inputs. - **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:** 21 Nov 2022 ## What is GHSA-cqvq-fvhr-v6hc? GHSA-cqvq-fvhr-v6hc is a denial of service vulnerability in tensorflow, published on 21 Nov 2022. ### Official description ### Impact Another instance of CVE-2022-35935, where `SobolSample` is vulnerable to a denial of service via assumed scalar inputs, was found and fixed. ```python import tensorflow as tf tf.raw_ops.SobolSample(dim=tf.constant([1,0]), num_results=tf.constant([1]), skip=tf.constant([1])) ``` ### Patches We have patched the issue in GitHub commits [c65c67f88ad770662e8f191269a907bf2b94b1bf](https://github.com/tensorflow/tensorflow/commit/c65c67f88ad770662e8f191269a907bf2b94b1bf) and [02400ea266bd811fc016a848445de1bbff3a23a0](https://github.com/tensorflow/tensorflow/commit/02400ea266bd811fc016a848445de1bbff3a23a0) The fix will be included in TensorFlow 2.11. We will also cherrypick both commits on TensorFlow 2.10.1, 2.9.3, and TensorFlow 2.8.4, as these are also affected and still in supported range. TensorFlow 2.7.4 will have the first commit cherrypicked. ### 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: - Kang Hong Jin from Singapore Management University - Neophytos Christou, Secure Systems Labs, Brown University - 刘力源, Information System & Security and Countermeasures Experiments Center, Beijing Institute of Technology - Pattarakrit Rattankul ## Which versions are affected by GHSA-cqvq-fvhr-v6hc? 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.8.4 | | `tensorflow` | PyPI | All versions | 2.8.4 | | `tensorflow` | PyPI | From 2.10.0 | 2.10.1 | | `tensorflow` | PyPI | From 2.10.0 | 2.10.1 | | `tensorflow` | PyPI | From 2.9.0 | 2.9.3 | | `tensorflow` | PyPI | From 2.9.0 | 2.9.3 | | `tensorflow-cpu` | PyPI | All versions | 2.8.4 | | `tensorflow-cpu` | PyPI | All versions | 2.8.4 | | `tensorflow-cpu` | PyPI | From 2.10.0 | 2.10.1 | | `tensorflow-cpu` | PyPI | From 2.10.0 | 2.10.1 | | `tensorflow-cpu` | PyPI | From 2.9.0 | 2.9.3 | | `tensorflow-cpu` | PyPI | From 2.9.0 | 2.9.3 | | `tensorflow-gpu` | PyPI | All versions | 2.8.4 | | `tensorflow-gpu` | PyPI | All versions | 2.8.4 | | `tensorflow-gpu` | PyPI | From 2.10.0 | 2.10.1 | | `tensorflow-gpu` | PyPI | From 2.10.0 | 2.10.1 | | `tensorflow-gpu` | PyPI | From 2.9.0 | 2.9.3 | | `tensorflow-gpu` | PyPI | From 2.9.0 | 2.9.3 | ## How do I fix GHSA-cqvq-fvhr-v6hc? Upgrade tensorflow to a fixed version for your release line: 2.8.4, 2.10.1 or 2.9.3. ## Is GHSA-cqvq-fvhr-v6hc being exploited? There is no known exploitation of GHSA-cqvq-fvhr-v6hc in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for GHSA-cqvq-fvhr-v6hc and fix it if it is affected. What it is: GHSA-cqvq-fvhr-v6hc is a denial of service vulnerability in tensorflow, published on 21 Nov 2022. Exploitation: There is no known exploitation of GHSA-cqvq-fvhr-v6hc in the wild and no public exploit code. Affected packages and fixed versions: - tensorflow (PyPI): affected all versions; fixed in 2.8.4 - tensorflow (PyPI): affected all versions; fixed in 2.8.4 - tensorflow (PyPI): affected from 2.10.0; fixed in 2.10.1 - tensorflow (PyPI): affected from 2.10.0; fixed in 2.10.1 - tensorflow (PyPI): affected from 2.9.0; fixed in 2.9.3 - tensorflow (PyPI): affected from 2.9.0; fixed in 2.9.3 - tensorflow-cpu (PyPI): affected all versions; fixed in 2.8.4 - tensorflow-cpu (PyPI): affected all versions; fixed in 2.8.4 - tensorflow-cpu (PyPI): affected from 2.10.0; fixed in 2.10.1 - tensorflow-cpu (PyPI): affected from 2.10.0; fixed in 2.10.1 - tensorflow-cpu (PyPI): affected from 2.9.0; fixed in 2.9.3 - tensorflow-cpu (PyPI): affected from 2.9.0; fixed in 2.9.3 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-cqvq-fvhr-v6hc/ (Markdown: https://insights.sbomify.com/GHSA-cqvq-fvhr-v6hc/index.md) ``` ## Sources - OSV: https://osv.dev/vulnerability/GHSA-cqvq-fvhr-v6hc --- From sbomify Insights: https://insights.sbomify.com/GHSA-cqvq-fvhr-v6hc/ Summaries are generated and may contain mistakes; the official description above is the record.