CHECK-failure in `UnsortedSegmentJoin`
Low2.5CVE-2021-29552 · Published May 21, 2021 · updated Jul 8, 2026
Affected versions
| Package | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI | < 2.1.4 | 2.1.4 |
| >= 2.2.0, < 2.2.3 | 2.2.3 | |
| >= 2.3.0, < 2.3.3 | 2.3.3 | |
| >= 2.4.0, < 2.4.2 | 2.4.2 |
Details and references
### Impact An attacker can cause a denial of service by controlling the values of `num_segments` tensor argument for `UnsortedSegmentJoin`: ```python import tensorflow as tf inputs = tf.constant([], dtype=tf.string) segment_ids = tf.constant([], dtype=tf.int32) num_segments = tf.constant([], dtype=tf.int32) separator = '' tf.raw_ops.UnsortedSegmentJoin( inputs=inputs, segment_ids=segment_ids, num_segments=num_segments, separator=separator) ``` This is because the [implementation](https://github.com/tensorflow/tensorflow/blob/a2a607db15c7cd01d754d37e5448d72a13491bdb/tensorflow/core/kernels/unsorted_segment_join_op.cc#L92-L93) assumes that the `num_segments` tensor is a valid scalar: ```cc const Tensor& num_segments_tensor = context->input(2); auto num_segments = num_segments_tensor.scalar<NUM_SEGMENTS_TYPE>()(); ``` Since the tensor is empty the `CHECK` involved in `.scalar<T>()()` that checks that the number of elements is exactly 1 will be invalidated and this would result in process termination. ### Patches We have patched the issue in GitHub commit [704866eabe03a9aeda044ec91a8d0c83fc1ebdbe](https://github.com/tensorflow/tensorflow/commit/704866eabe03a9aeda044ec91a8d0c83fc1ebdbe). The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.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 Ying Wang and Yakun Zhang of Baidu X-Team.
- CVSS 3.1
- CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L
- Severity from
- GitHub (reviewed advisory)
- Weakness
- CWE-617
- Also known as
- BIT-tensorflow-2021-29552, CVE-2021-29552, PYSEC-2021-189, PYSEC-2021-480, PYSEC-2021-678
- github.com/tensorflow/tensorflow/security/advisories/GHSA-jhq9-wm9m-cf89
- nvd.nist.gov/vuln/detail/CVE-2021-29552
- github.com/tensorflow/tensorflow/commit/704866eabe03a9aeda044ec91a8d0c83fc1ebdbe
- github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2021-480.yaml
- github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2021-678.yaml
- github.com/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2021-189.yaml
- github.com/tensorflow/tensorflow
More TensorFlow advisories
All TensorFlow| Date | Advisory | Severity | Fixed in |
|---|---|---|---|
| May 212021 | Heap buffer overflow in `RaggedBinCount` CVE-2021-29512Low2.5fixed in 2.3.3, 2.4.2 | Low2.5 | 2.3.3, 2.4.2 |
| May 212021 | Type confusion during tensor casts lead to dereferencing null pointers CVE-2021-29513Low2.5fixed in 2.1.4, 2.2.3, 2.3.3, 2.4.2 | Low2.5 | 2.1.4, 2.2.3, 2.3.3, 2.4.2 |
| May 212021 | Heap out of bounds write in `RaggedBinCount` CVE-2021-29514Low2.5fixed in 2.3.3, 2.4.2 | Low2.5 | 2.3.3, 2.4.2 |
| May 212021 | Reference binding to null pointer in `MatrixDiag*` ops CVE-2021-29515Low2.5fixed in 2.1.4, 2.2.3, 2.3.3, 2.4.2 | Low2.5 | 2.1.4, 2.2.3, 2.3.3, 2.4.2 |
| May 212021 | Null pointer dereference via invalid Ragged Tensors CVE-2021-29516Low2.5fixed in 2.1.4, 2.2.3, 2.3.3, 2.4.2 | Low2.5 | 2.1.4, 2.2.3, 2.3.3, 2.4.2 |
| May 212021 | Division by zero in `Conv3D` CVE-2021-29517Low2.5fixed in 2.1.4, 2.2.3, 2.3.3, 2.4.2 | Low2.5 | 2.1.4, 2.2.3, 2.3.3, 2.4.2 |