Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
GHSA-6gmv-pjp9-p8w8
No affected components available
Impact
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];
}
Patches
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.
For more information
Please consult our security guide 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.
The vulnerability can be exploited over the network without needing physical access. It is easy for an attacker to exploit this vulnerability. An attacker needs basic access or low-level privileges. No user interaction is needed for the attacker to exploit this vulnerability. The impact is confined to the system where the vulnerability exists. There is a high impact on the confidentiality of the information. There is a high impact on the availability of the system.
Exploitation activity has been observed. Apply available patches or mitigations urgently.
The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
Browse More
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard