TensorFlow is an end-to-end open source platform for machine learning. An attacker can trigger a dereference of a null pointer in `tf.raw_ops.StringNGrams`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/1cdd4da14282210cc759e468d9781741ac7d01bf/tensorflow/core/kernels/string_ngrams_op.cc#L67-L74) does not fully validate the `data_splits` argument. This would result in `ngrams_data`(https://github.com/tensorflow/tensorflow/blob/1cdd4da14282210cc759e468d9781741ac7d01bf/tensorflow/core/kernels/string_ngrams_op.cc#L106-L110) to be a null pointer when the output would be computed to have 0 or negative size. Later writes to the output tensor would then cause a null pointer dereference. 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.
References
Link | Resource |
---|---|
https://github.com/tensorflow/tensorflow/commit/ba424dd8f16f7110eea526a8086f1a155f14f22b | Patch Third Party Advisory |
https://github.com/tensorflow/tensorflow/security/advisories/GHSA-xqfj-35wv-m3cr | Exploit Patch Third Party Advisory |
Configurations
Configuration 1 (hide)
|
Information
Published : 2021-05-14 13:15
Updated : 2021-05-20 09:21
NVD link : CVE-2021-29541
Mitre link : CVE-2021-29541
JSON object : View
CWE
CWE-476
NULL Pointer Dereference
Products Affected
- tensorflow