CVSS 3.1
5.5 mediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HMedium (5.5) in google tensorflow. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in tensorflow 2.1.4, 2.2.3, 2.3.3.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:Htensorflow (PyPI): fixed in 2.1.4, 2.2.3, 2.3.3, 2.4.2tensorflow-cpu (PyPI): fixed in 2.1.4, 2.2.3, 2.3.3, 2.4.2tensorflow-gpu (PyPI): fixed in 2.1.4, 2.2.3, 2.3.3, 2.4.2Explain CVE-2021-29615 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2021-29615?via=ask-ai-copy and https://cve.bz/cve/CVE-2021-29615?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2021-29615 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| google:tensorflow | before 2.1.4 |
| google:tensorflow | from 2.2.0 before 2.2.3 |
| google:tensorflow | from 2.3.0 before 2.3.3 |
| google:tensorflow | from 2.4.0 before 2.4.2 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-qw5h-7f53-xrp6 | PyPI | tensorflow | <2.1.4 | 2.1.4 |
| GHSA-qw5h-7f53-xrp6 | PyPI | tensorflow | >=2.2.0 <2.2.3 | 2.2.3 |
| GHSA-qw5h-7f53-xrp6 | PyPI | tensorflow | >=2.3.0 <2.3.3 | 2.3.3 |
| GHSA-qw5h-7f53-xrp6 | PyPI | tensorflow | >=2.4.0 <2.4.2 | 2.4.2 |
| GHSA-qw5h-7f53-xrp6 | PyPI | tensorflow-cpu | <2.1.4 | 2.1.4 |
| GHSA-qw5h-7f53-xrp6 | PyPI | tensorflow-cpu | >=2.2.0 <2.2.3 | 2.2.3 |
| GHSA-qw5h-7f53-xrp6 | PyPI | tensorflow-cpu | >=2.3.0 <2.3.3 | 2.3.3 |
| GHSA-qw5h-7f53-xrp6 | PyPI | tensorflow-cpu | >=2.4.0 <2.4.2 | 2.4.2 |
| GHSA-qw5h-7f53-xrp6 | PyPI | tensorflow-gpu | <2.1.4 | 2.1.4 |
| GHSA-qw5h-7f53-xrp6 | PyPI | tensorflow-gpu | >=2.2.0 <2.2.3 | 2.2.3 |
| GHSA-qw5h-7f53-xrp6 | PyPI | tensorflow-gpu | >=2.3.0 <2.3.3 | 2.3.3 |
| GHSA-qw5h-7f53-xrp6 | PyPI | tensorflow-gpu | >=2.4.0 <2.4.2 | 2.4.2 |
| PYSEC-2021-252 | PyPI | tensorflow | <2.1.4 >=2.2.0 <2.2.3 >=2.3.0 <2.3.3 >=2.4.0 <2.4.2 | 2.1.4, 2.2.3, 2.3.3, 2.4.2 |
| PYSEC-2021-543 | PyPI | tensorflow-cpu | <2.1.4 >=2.2.0 <2.2.3 >=2.3.0 <2.3.3 >=2.4.0 <2.4.2 | 2.1.4, 2.2.3, 2.3.3, 2.4.2 |
| PYSEC-2021-741 | PyPI | tensorflow-gpu | <2.1.4 >=2.2.0 <2.2.3 >=2.3.0 <2.3.3 >=2.4.0 <2.4.2 | 2.1.4, 2.2.3, 2.3.3, 2.4.2 |
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.