CVE-2022-21728High· 8.1▾ MidnightPoC availableOut of bounds read in Tensorflow
▾ Midnight zone — Critical, or high with PoC / in-the-wild
impact 44.6 · likelihood 0.2 · exploitation 12
A public proof-of-concept already exists for this vulnerability — see Exploit availability below.
Public exploit / PoC code seen in 1 source. Availability, not in-the-wild use.
Exploit-prediction probability, daily snapshots since Jul 13.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
1.1%
1.1% → 1.1%
1 GitHub repo
Last analysed / modified upstream
The implementation of shape inference for ReverseSequence does not fully validate the value of batch_dim and can result in a heap OOB read:
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:
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 would access elements before the start of an array:
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];
}
We have patched the issue in GitHub 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.
Please consult our security guide for more information regarding the security model and how to contact us with issues and questions.
This vulnerability has been reported by Yu Tian of Qihoo 360 AIVul Team.
tensorflow < 2.5.3tensorflow >= 2.6.0, < 2.6.3tensorflow >= 2.7.0, < 2.7.1tensorflow-cpu < 2.5.3tensorflow-cpu >= 2.6.0, < 2.6.3tensorflow-cpu >= 2.7.0, < 2.7.1tensorflow-gpu < 2.5.3tensorflow-gpu >= 2.6.0, < 2.6.3tensorflow-gpu >= 2.7.0, < 2.7.1Upgrade to a patched release:
tensorflow 2.5.3tensorflow 2.6.3tensorflow 2.7.1tensorflow-cpu 2.5.3tensorflow-cpu 2.6.3tensorflow-cpu 2.7.1tensorflow-gpu 2.5.3tensorflow-gpu 2.6.3tensorflow-gpu 2.7.1Field changes observed since this record was first indexed.
Connected by shared product, vendor, weakness, or advisory.
CVE-2021-29541Low· 2.5Null pointer dereference in `StringNGrams`
CVE-2021-29525Low· 2.5Division by 0 in `Conv2DBackpropInput`
CVE-2021-29527Low· 2.5Division by 0 in `QuantizedConv2D`
CVE-2021-29524Low· 2.5Division by 0 in `Conv2DBackpropFilter`
CVE-2020-15207High· 8.7Segfault and data corruption in tensorflow-lite
CVE-2021-29535Low· 2.5Heap buffer overflow in `QuantizedMul`