CVE-2020-26271: Heap out of bounds access in MakeEdge in TensorFlow
(updated )
Under certain cases, loading a saved model can result in accessing uninitialized memory while building the computation graph. The MakeEdge
function creates an edge between one output tensor of the src
node (given by output_index
) and the input slot of the dst
node (given by input_index
). This is only possible if the types of the tensors on both sides coincide, so the function begins by obtaining the corresponding DataType
values and comparing these for equality:
DataType src_out = src->output_type(output_index);
DataType dst_in = dst->input_type(input_index);
//...
However, there is no check that the indices point to inside of the arrays they index into. Thus, this can result in accessing data out of bounds of the corresponding heap allocated arrays.
In most scenarios, this can manifest as unitialized data access, but if the index points far away from the boundaries of the arrays this can be used to leak addresses from the library.
References
- github.com/advisories/GHSA-q263-fvxm-m5mw
- github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2020-302.yaml
- github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2020-337.yaml
- github.com/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2020-257.yaml
- github.com/tensorflow/tensorflow/commit/0cc38aaa4064fd9e79101994ce9872c6d91f816b
- github.com/tensorflow/tensorflow/security/advisories/GHSA-q263-fvxm-m5mw
- nvd.nist.gov/vuln/detail/CVE-2020-26271
Detect and mitigate CVE-2020-26271 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →