CVSS 3.1
5.3 mediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:LMedium (5.3). EPSS 1.7% estimated probability of exploitation activity in the next 30 days. Fixed in numpy 1.10.0, 1.22.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:Lnumpy (PyPI): fixed in 1.22, 1.10.0Explain CVE-2021-34141 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2021-34141?via=ask-ai-copy and https://cve.bz/cve/CVE-2021-34141?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-34141 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 |
|---|---|
| numpy:numpy | before 1.22.0 |
| oracle:communications_cloud_native_core_policy | 22.1.3 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-fpfv-jqm9-f5jm | PyPI | numpy | <1.22 | 1.22 |
| PYSEC-2021-855 | PyPI | numpy | >=1.9.0 <1.10.0 | 1.10.0 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13, 14 | numpy | no fix listed | DEBIAN-CVE-2021-34141 |
| Ubuntu | 20.04:LTS | numpy | 1:1.17.4-5ubuntu3.1 | UBUNTU-CVE-2021-34141 USN-5763-1 |
| Ubuntu | 22.04:LTS | numpy | 1:1.21.5-1ubuntu22.04.1 | UBUNTU-CVE-2021-34141 USN-5763-1 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.
Red Hat rates this Low.
Red Hat products using an affected version of numpy are at essentially no risk of exploitation from this vulnerability given the high privileges and high complexity required for successful exploitation. The preconditions necessary to exploit are:
1) A privileged user or a non-standard configuration of numpy to provide a non-validated dtype string.
2) The ability to execute arbitrary code at runtime.
More specifically:
1) A user must be able to provide a non-validated dtype string to be parsed by numpy; something that would require a privileged user or a non-standard configuration.
2) Even then, the specific code block where the vulnerability is present cannot be reached without the attacker modifying the runtime environment to prevent an error from being thrown earlier in the code (before the string comparison), when the code checks an internal dictionary to determine the validity of the user-provided string type. Such runtime modifications would require executing arbitrary Python code.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 6 | numpy | Not affected | |
| Red Hat Enterprise Linux 7 | numpy | Not affected | |
| Red Hat Enterprise Linux 8 | inkscape:flatpak/numpy | Fix deferred | |
| Red Hat Enterprise Linux 8 | numpy | Fix deferred | |
| Red Hat Enterprise Linux 8 | python27:2.7/numpy | Fix deferred | |
| Red Hat Enterprise Linux 8 | python38:3.8/numpy | Fix deferred | |
| Red Hat Enterprise Linux 8 | python39:3.9/numpy | Fix deferred | |
| Red Hat Enterprise Linux 9 | numpy | Will not fix | |
| Red Hat OpenStack Platform 13 (Queens) | numpy | Not affected | |
| Red Hat OpenStack Platform 16.1 | numpy | Not affected | |
| Red Hat OpenStack Platform 16.2 | numpy | Not affected | |
| Red Hat Software Collections | python27-numpy | Not affected | |
| Red Hat Software Collections | rh-python38-numpy | Fix deferred |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2021-34141.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-697 (29).