CVE-2021-41211: Heap OOB read in shape inference for `QuantizeV2`
Impact The shape inference code for QuantizeV2 can trigger a read outside of bounds of heap allocated array:
python import tensorflow as tf
@tf.function def test(): data=tf.rawops.QuantizeV2( input=[1.0,1.0], minrange=[1.0,10.0], maxrange=[1.0,10.0], T=tf.qint32, mode='MINCOMBINED', roundmode='HALFTOEVEN', narrowrange=False, axis=-100, ensureminimumrange=10) return data
test()
This occurs whenever axis is a negative value less than -1. In this case, we are accessing data before the start of a heap buffer: cc int axis = -1; Status s = c->GetAttr("axis", &axis); if (!s.ok() && s.code() != error::NOTFOUND) { return s; } ... if (axis != -1) { ... TFRETURNIFERROR( c->Merge(c->Dim(minmax, 0), c->Dim(input, axis), &depth)); }
The code allows axis to be an optional argument (s would contain an error::NOTFOUND error code). Otherwise, it assumes that axis is a valid index into the dimensions of the input tensor. If axis is less than -1 then this results in a heap OOB read. Patches We have patched the issue in GitHub commit a0d64445116c43cf46a5666bd4eee28e7a82f244. The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, as this version is the only one that is also affected. 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 members of the Aivul Team from Qihoo 360.
Other sources
TensorFlow is an open source platform for machine learning. In affected versions the shape inference code for QuantizeV2 can trigger a read outside of bounds of heap allocated array. This occurs whenever axis is a negative value less than -1. In this case, we are accessing data before the start of a heap buffer. The code allows axis to be an optional argument (s would contain an error::NOTFOUND error code). Otherwise, it assumes that axis is a valid index into the dimensions of the input tensor. If axis is less than -1 then this results in a heap OOB read. The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, as this version is the only one that is also affected.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2021-41211?
CVE-2021-41211 is classified as a high severity vulnerability due to the potential for heap memory corruption.
How do I fix CVE-2021-41211?
You can fix CVE-2021-41211 by upgrading TensorFlow to version 2.6.1 or later.
Which versions of TensorFlow are affected by CVE-2021-41211?
CVE-2021-41211 affects TensorFlow version 2.6.0.
What is the impact of CVE-2021-41211?
The impact of CVE-2021-41211 includes the potential for a read outside of the bounds of a heap-allocated array.
Is CVE-2021-41211 specific to any TensorFlow packages?
Yes, CVE-2021-41211 specifically affects the tensorflow-gpu, tensorflow-cpu, and tensorflow packages in version 2.6.0.