CVE-2020-15208
Description
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, when determining the common dimension size of two tensors, TFLite uses a `DCHECK` which is no-op outside of debug compilation modes. Since the function always returns the dimension of the first tensor, malicious attackers can craft cases where this is larger than that of the second tensor. In turn, this would result in reads/writes outside of bounds since the interpreter will wrongly assume that there is enough data in both tensors. The issue is patched in commit 8ee24e7949a203d234489f9da2c5bf45a7d5157d, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
OS impact
Debian Fixed 2 releases
| Version | Status | Fixed in |
|---|---|---|
| sid | Fixed | 0 |
| forky | Fixed | 0 |
Package impact
| Ecosystem | Package | Vulnerable | Fixed |
|---|---|---|---|
| PyPI | tensorflow | <1.15.4 | 1.15.4 |
| PyPI | tensorflow | >=2.0.0,<2.0.3 | 2.0.3 |
| PyPI | tensorflow | >=2.1.0,<2.1.2 | 2.1.2 |
| PyPI | tensorflow | >=2.2.0,<2.2.1 | 2.2.1 |
| PyPI | tensorflow | >=2.3.0,<2.3.1 | 2.3.1 |
| PyPI | tensorflow-cpu | <1.15.4 | 1.15.4 |
| PyPI | tensorflow-cpu | >=2.0.0,<2.0.3 | 2.0.3 |
| PyPI | tensorflow-cpu | >=2.1.0,<2.1.2 | 2.1.2 |
| PyPI | tensorflow-cpu | >=2.2.0,<2.2.1 | 2.2.1 |
| PyPI | tensorflow-cpu | >=2.3.0,<2.3.1 | 2.3.1 |
| PyPI | tensorflow-gpu | <1.15.4 | 1.15.4 |
| PyPI | tensorflow-gpu | >=2.0.0,<2.0.3 | 2.0.3 |
| PyPI | tensorflow-gpu | >=2.1.0,<2.1.2 | 2.1.2 |
| PyPI | tensorflow-gpu | >=2.2.0,<2.2.1 | 2.2.1 |
| PyPI | tensorflow-gpu | >=2.3.0,<2.3.1 | 2.3.1 |
| PyPI | tensorflow-gpu | <8ee24e7949a203d234489f9da2c5bf45a7d5157d||>=2.3.0,<2.3.1 | 8ee24e7949a203d234489f9da2c5bf45a7d5157d |
| PyPI | tensorflow-cpu | <8ee24e7949a203d234489f9da2c5bf45a7d5157d||>=2.3.0,<2.3.1 | 8ee24e7949a203d234489f9da2c5bf45a7d5157d |
| PyPI | tensorflow | <8ee24e7949a203d234489f9da2c5bf45a7d5157d||>=2.3.0,<2.3.1 | 8ee24e7949a203d234489f9da2c5bf45a7d5157d |
References
- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-mxjj-953w-2c2v
- https://nvd.nist.gov/vuln/detail/CVE-2020-15208
- https://github.com/tensorflow/tensorflow/commit/8ee24e7949a203d234489f9da2c5bf45a7d5157d
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2020-288.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2020-323.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2020-131.yaml
- https://github.com/tensorflow/tensorflow
- https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1
- http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00065.html
- https://security-tracker.debian.org/tracker/CVE-2020-15208
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.