Advisory

PYSEC-2020-294

Also known as: BIT-tensorflow-2020-15214, CVE-2020-15214, GHSA-p2cq-cprg-frvm, PYSEC-2020-137, PYSEC-2020-329

Summary

The record has no summary.

Details

In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger a write out bounds / segmentation fault if the segment ids are not sorted. Code assumes that the segment ids are in increasing order, using the last element of the tensor holding them to determine the dimensionality of output tensor. This results in allocating insufficient memory for the output tensor and in a write outside the bounds of the output array. This usually results in a segmentation fault, but depending on runtime conditions it can provide for a write gadget to be used in future memory corruption-based exploits. The issue is patched in commit 204945b19e44b57906c9344c0d00120eeeae178a and is released in TensorFlow versions 2.2.1, or 2.3.1. A potential workaround would be to add a custom Verifier to the model loading code to ensure that the segment ids are sorted, although this only handles the case when the segment ids are stored statically in the model. A similar validation could be done if the segment ids are generated at runtime between inference steps. If the segment ids are generated as outputs of a tensor during inference steps, then there are no possible workaround and users are advised to upgrade to patched code.

Severity

Not rated by the source.

Dates

Published
2020-09-25 19:15 UTC
Modified
2023-12-06 01:00 UTC

Affected packages and fixes

tensorflow-cpu

PyPI · All systems

Affected

  • introduced 2.2.0, fixed 2.2.1, introduced 2.3.0, fixed 2.3.1 (ecosystem)

Fixed versions

2.2.1, 2.3.1

Fix

  • Fixed version 2.2.1
    pip install --upgrade tensorflow-cpu==2.2.1
  • Fixed version 2.3.1
    pip install --upgrade tensorflow-cpu==2.3.1

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: PyPA Advisory Database · CC BY 4.0

Sources & licences