Spurious warning via prefix-only typecode comparison
Published Dec 17, 2021 · Updated Aug 4, 2024
Incorrect comparison in NumPy before 1.22.0 allows attackers to trigger a spurious deprecation-warning path with crafted type strings. The _convert_from_str function in descriptor.c compares only the known typecode length, so a longer string sharing a deprecated typecode prefix compares equal. The input must reach dtype-string conversion; upstream states that the behavior only controls whether a deprecation warning is emitted and is completely harmless.
Summary
What happened
Incorrect comparison in NumPy before 1.22.0 allows attackers to trigger a spurious deprecation-warning path with crafted type strings. The _convert_from_str function in descriptor.c compares only the known typecode length, so a longer string sharing a deprecated typecode prefix compares equal. The input must reach dtype-string conversion; upstream states that the behavior only controls whether a deprecation warning is emitted and is completely harmless.
The record
- CVE
- CVE-2021-34141
- Published
- Dec 17, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-697
- Attack vector
- network
- Privileges
- unauthenticated
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