Interpreter crash via unchecked descriptor allocation
Published Dec 17, 2021 · Updated Aug 4, 2024
Null pointer dereference in NumPy before 1.19.1 allows attackers to crash the Python interpreter by repeatedly creating sort arrays. PyArray_DescrNew can return NULL after an allocation failure, and a numpy.sort call site reads the returned descriptor without checking it. Triggering the dereference requires memory exhaustion at that exact allocation point and permission to execute NumPy functions, so NumPy disputes that the bug crosses a security boundary beyond the caller's existing process privileges.
Summary
What happened
Null pointer dereference in NumPy before 1.19.1 allows attackers to crash the Python interpreter by repeatedly creating sort arrays. PyArray_DescrNew can return NULL after an allocation failure, and a numpy.sort call site reads the returned descriptor without checking it. Triggering the dereference requires memory exhaustion at that exact allocation point and permission to execute NumPy functions, so NumPy disputes that the bug crosses a security boundary beyond the caller's existing process privileges.
The record
- CVE
- CVE-2021-41495
- Published
- Dec 17, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Dec 17, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo