CVE-2021-34141: Incorrect Comparison in NumPy

CVE-2021-34141 · Severity: low · CVSS 3.1 · Published 2021-12-17

Incomplete string comparison in the numpy.core component in NumPy1.9.x, which allows attackers to fail the APIs via constructing specific string objects.

Technologies: numpy (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2021-34141 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2021-34141 being exploited in the wild.
How severe is CVE-2021-34141?
Low severity, with a CVSS score of 3.1, published 17 December 2021.
Which products and versions are affected?
numpy (PyPI) ECOSYSTEM:introduced=0,fixed=1.22, ECOSYSTEM:introduced=1.9.0,fixed=1.10.0.
Is there a fix for CVE-2021-34141?
Yes. numpy (PyPI): upgrade to 1.10.0, 1.22 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2021-34141?
Check whether you run numpy (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • numpy (PyPI): upgrade to 1.10.0, 1.22 or later
    pip install "numpy>=1.22"

Affected products

  • numpy (PyPI) ECOSYSTEM:introduced=0,fixed=1.22, ECOSYSTEM:introduced=1.9.0,fixed=1.10.0

Identifiers

  • CVE-2021-34141
  • GHSA-fpfv-jqm9-f5jm
  • PYSEC-2021-855

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.