Skip to content
TensorFlowGHSA-6gmv-pjp9-p8w8

Out of bounds read in Tensorflow

High8.1CVE-2022-21728 · Published Feb 9, 2022 · updated Sep 10, 2026

GitHub advisory

Affected versions

PackageAffectedFixed in
tensorflow
PyPI
< 2.5.32.5.3
>= 2.6.0, < 2.6.32.6.3
>= 2.7.0, < 2.7.12.7.1
Details and references

### Impact The [implementation of shape inference for `ReverseSequence`](https://github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/core/ops/array_ops.cc#L1636-L1671) does not fully validate the value of `batch_dim` and can result in a heap OOB read: ```python import tensorflow as tf @tf.function def test(): y = tf.raw_ops.ReverseSequence( input = ['aaa','bbb'], seq_lengths = [1,1,1], seq_dim = -10, batch_dim = -10 ) return y test() ``` There is a check to make sure the value of `batch_dim` does not go over the rank of the input, but there is no check for negative values: ```cc const int32_t input_rank = c->Rank(input); if (batch_dim >= input_rank) { return errors::InvalidArgument( "batch_dim must be < input rank: ", batch_dim, " vs. ", input_rank); } // ... DimensionHandle batch_dim_dim = c->Dim(input, batch_dim); ``` Negative dimensions are allowed in some cases to mimic Python's negative indexing (i.e., indexing from the end of the array), however if the value is too negative then [the implementation of `Dim`](https://github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/core/framework/shape_inference.h#L415-L428) would access elements before the start of an array: ```cc DimensionHandle Dim(ShapeHandle s, int64_t idx) { if (!s.Handle() || s->rank_ == kUnknownRank) { return UnknownDim(); } return DimKnownRank(s, idx); } · static DimensionHandle DimKnownRank(ShapeHandle s, int64_t idx) { CHECK_NE(s->rank_, kUnknownRank); if (idx < 0) { return s->dims_[s->dims_.size() + idx]; } return s->dims_[idx]; } ``` ### Patches We have patched the issue in GitHub commit [37c01fb5e25c3d80213060460196406c43d31995](https://github.com/tensorflow/tensorflow/commit/37c01fb5e25c3d80213060460196406c43d31995). The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, 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 Yu Tian of Qihoo 360 AIVul Team.

CVSS 3.1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
Severity from
GitHub (reviewed advisory)
Weakness
CWE-125
Also known as
BIT-tensorflow-2022-21728, CVE-2022-21728, PYSEC-2022-107, PYSEC-2022-52, PYSEC-2026-3121

More TensorFlow advisories

All TensorFlow
DateAdvisory
Feb 92022Out of bounds read in Tensorflow
CVE-2022-21726High8.1fixed in 2.5.3, 2.6.3, 2.7.1
Feb 92022Integer overflow in Tensorflow
CVE-2022-21727High7.6fixed in 2.5.3, 2.6.3, 2.7.1
Feb 92022Out of bounds read in Tensorflow
CVE-2022-21730High8.1fixed in 2.5.3, 2.6.3, 2.7.1
Feb 92022Out of bounds read and write in Tensorflow
CVE-2022-23574High8.8fixed in 2.5.3, 2.6.3, 2.7.1
Feb 92022Memory leak in decoding PNG images
CVE-2022-23585Medium4.3fixed in 2.5.3, 2.6.3, 2.7.1
Feb 92022Uninitialized variable access in Tensorflow
CVE-2022-23573High7.6fixed in 2.5.3, 2.6.3, 2.7.1

Critical advisories by email

Wednesdays: the week’s critical and high advisories in the AI and data stack, with the fixed versions. Only in weeks that have some.

Double opt-in. Unsubscribe any time.