PyPI: tensorflow-rocm-enhanced
CVE-2021-37669
Safety vulnerability ID: SFTY-20210812-93532
Safety legacy ID: pyup.io-58030
Tensorflow-rocm-enhanced version 2.3.4 and 2.4.3 include a fix for CVE-2021-37669: In affected versions, an attacker can cause denial of service in applications serving models using "tf.raw_ops.NonMaxSuppressionV5" by triggering a division by 0. The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/image/non_max_suppression_op.cc#L170-L271) uses a user controlled argument to resize a "std::vector". However, as "std::vector::resize" takes the size argument as a "size_t" and "output_size" is an "int", there is an implicit conversion to unsigned. If the attacker supplies a negative value, this conversion results in a crash. A similar issue occurs in "CombinedNonMaxSuppression". The Tensorflow team has patched the issue in GitHub commit 3a7362750d5c372420aa8f0caf7bf5b5c3d0f52d and commit b5cdbf12ffcaaffecf98f22a6be5a64bb96e4f58. https://github.com/tensorflow/tensorflow/security/advisories/GHSA-vmjw-c2vp-p33c https://github.com/tensorflow/tensorflow/commit/3a7362750d5c372420aa8f0caf7bf5b5c3d0f52d https://github.com/tensorflow/tensorflow/commit/b5cdbf12ffcaaffecf98f22a6be5a64bb96e4f58
Overview
Crash in NMS ops caused by integer conversion to unsigned
Advisory
Tensorflow-rocm-enhanced version 2.3.4 and 2.4.3 include a fix for CVE-2021-37669: In affected versions, an attacker can cause denial of service in applications serving models using "tf.raw_ops.NonMaxSuppressionV5" by triggering a division by 0. The implementation (https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/image/non_max_suppression_op.cc#L170-L271) uses a user controlled argument to resize a "std::vector". However, as "std::vector::resize" takes the size argument as a "size_t" and "output_size" is an "int", there is an implicit conversion to unsigned. If the attacker supplies a negative value, this conversion results in a crash. A similar issue occurs in "CombinedNonMaxSuppression". The Tensorflow team has patched the issue in GitHub commit 3a7362750d5c372420aa8f0caf7bf5b5c3d0f52d and commit b5cdbf12ffcaaffecf98f22a6be5a64bb96e4f58. https://github.com/tensorflow/tensorflow/security/advisories/GHSA-vmjw-c2vp-p33c https://github.com/tensorflow/tensorflow/commit/3a7362750d5c372420aa8f0caf7bf5b5c3d0f52d https://github.com/tensorflow/tensorflow/commit/b5cdbf12ffcaaffecf98f22a6be5a64bb96e4f58
Affected Package
Also affects
---
How to Fix
Mitigation and Workarounds
---
Vulnerable Functions
Functions linked to known vulnerabilities.
References
- https://getsafety.com/vulnerabilities/SFTY-20210812-93532/CVE-2021-37669
- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-vmjw-c2vp-p33c
- https://nvd.nist.gov/vuln/detail/CVE-2021-37669
- https://github.com/tensorflow/tensorflow/commit/3a7362750d5c372420aa8f0caf7bf5b5c3d0f52d
- https://github.com/tensorflow/tensorflow/commit/b5cdbf12ffcaaffecf98f22a6be5a64bb96e4f58
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2021-582.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2021-780.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2021-291.yaml
- https://github.com/advisories/GHSA-vmjw-c2vp-p33c
Verified by Safety
Our Cybersecurity Intelligence Team reviewed this vulnerability. We combine public data with our own research to find issues not yet reported to public sources.
Learn more
