Skip to content
Noroxi
NVD / CVE Program· CNA mitre

CVE-2021-33430: A Buffer Overflow vulnerability exists in NumPy 1.9.x in the PyArray_NewFromDescr_int function of ctors.c when specifying arrays of large di

Noroxi assessment

Priority: Monitor (action score 21/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 1.5% (FIRST EPSS); higher than 74.7% of all records.
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: numpy (Debian:12) 1:1.21.4-2; dxflib (openSUSE:Leap 15.3) 3.17.0-bp153.2.3.1; python-numpy (openSUSE:Leap 15.3) 1.17.3-10.1.

Low priority for now. Upgrade to numpy (Debian:12) 1:1.21.4-2; dxflib (openSUSE:Leap 15.3) 3.17.0-bp153.2.3.1; python-numpy (openSUSE:Leap 15.3) 1.17.3-10.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

A Buffer Overflow vulnerability exists in NumPy 1.9.x in the PyArray_NewFromDescr_int function of ctors.c when specifying arrays of large dimensions (over 32) from Python code, which could let a malicious user cause a Denial of Service. NOTE: The vendor does not agree this is a vulneraility; In (very limited) circumstances a user may be able provoke the buffer overflow, the user is most likely already privileged to at least provoke denial of service by exhausting memory. Triggering this further requires the use of uncommon API (complicated structured dtypes), which is very unlikely to be available to an unprivileged user

MediumCVSS 5.3 · v3.1—No exploit Fix available
Published
Dec 17, 2021
Updated
Jun 16, 2026
EPSS
1.5% · 74th percentile

Report tools

JSON

Action score

21

Monitor

Low priority for now.

CVSS
21 / 40 · 5.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.5%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2021-33430

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
numpynumpy

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • numpy numpy1.9.0 and later · up to 1.9.3 inclusive

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12numpybefore 1:1.21.4-21:1.21.4-2
openSUSE:Leap 15.3dxflibbefore 3.17.0-bp153.2.3.13.17.0-bp153.2.3.1
openSUSE:Leap 15.3python-numpybefore 1.17.3-10.11.17.3-10.1
openSUSE:Leap 15.3python-numpy_1_17_3-gnu-hpcbefore 1.17.3-10.11.17.3-10.1
openSUSE:Leap 15.3python2-numpybefore 1.16.5-150200.3.5.11.16.5-150200.3.5.1
openSUSE:Leap 15.4python-numpy_1_16_5-gnu-hpcbefore 1.16.5-150200.3.5.11.16.5-150200.3.5.1
openSUSE:Tumbleweedpython-numbabefore 0.61.0-1.10.61.0-1.1
openSUSE:Tumbleweedpython-numpybefore 1.25.2-2.11.25.2-2.1
openSUSE:Tumbleweedpython-numpybefore 2.4.6-1.12.4.6-1.1
openSUSE:Tumbleweedpython-numpy1before 1.26.4-1.11.26.4-1.1
PyPInumpyfrom 1.9.0 · before 1.211.21
PyPInumpyfrom 1.9.0 · before 1.10.01.10.0
Red Hat:openstack:16.1::el8numpybefore 1:1.17.0-8.el8ost1:1.17.0-8.el8ost
Red Hat:openstack:16.1::el8numpy-debugsourcebefore 1:1.17.0-8.el8ost1:1.17.0-8.el8ost
Red Hat:openstack:16.1::el8python3-numpybefore 1:1.17.0-8.el8ost1:1.17.0-8.el8ost
Red Hat:openstack:16.1::el8python3-numpy-debuginfobefore 1:1.17.0-8.el8ost1:1.17.0-8.el8ost
Red Hat:openstack:16.1::el8python3-numpy-f2pybefore 1:1.17.0-8.el8ost1:1.17.0-8.el8ost
SUSE:Linux Enterprise High Performance Computing 15-ESPOSpython-numpy_1_16_5-gnu-hpcbefore 1.16.5-150000.1.9.11.16.5-150000.1.9.1
SUSE:Linux Enterprise High Performance Computing 15-ESPOSpython2-numpybefore 1.16.5-150000.1.9.11.16.5-150000.1.9.1
SUSE:Linux Enterprise Module for HPC 12python-numpy_1_13_3-gnu-hpcbefore 1.13.3-4.12.11.13.3-4.12.1
SUSE:Linux Enterprise Module for HPC 15 SP3python-numpy_1_16_5-gnu-hpcbefore 1.16.5-150200.3.5.11.16.5-150200.3.5.1
SUSE:Linux Enterprise Module for Python 2 15 SP3python2-numpybefore 1.16.5-150200.3.5.11.16.5-150200.3.5.1
SUSE:Linux Enterprise Real Time 15 SP2python-numpybefore 1.17.3-10.11.17.3-10.1
SUSE:Linux Enterprise Real Time 15 SP2python-numpy_1_17_3-gnu-hpcbefore 1.17.3-10.11.17.3-10.1

+2

Other highest-scoring records for the same primary product.

  • CVE-2019-6446An issue was discovered in NumPy before 1.16.3.
    47Plan
  • CVE-2017-12852The numpy.pad function in Numpy 1.13.1 and older versions is missing input validation.
    31Monitor
  • CVE-2021-34141An incomplete string comparison in the numpy.core component in NumPy before 1.22.0 allows attackers to trigger slightly incorrect copying by
    22Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2014-1858Jan 8, 2018 · __init__.py in f2py in NumPy before 1.8.1 allows local users to write to arbitrary files via a symlink attack on a temporary file.
    22Monitor
  • ← EarlierCVE-2014-1859Jan 8, 2018 · (1) core/tests/test_memmap.py, (2) core/tests/test_multiarray.py, (3) f2py/f2py2e.py, and (4) lib/tests/test_io.py in NumPy before 1.8.1 all
    22Monitor
  • Later →CVE-2021-41495Dec 17, 2021 · Null Pointer Dereference vulnerability exists in numpy.sort in NumPy &lt and 1.19 in the PyArray_DescrNew function due to missing return-val
    21Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:numpy1:1.21.4-2 · Debian:12Package registry (OSV)
opensuse:dxflib3.17.0-bp153.2.3.1 · openSUSE:Leap 15.3Package registry (OSV)
opensuse:python-numba0.61.0-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:python-numpy1.17.3-10.1 · openSUSE:Leap 15.3Package registry (OSV)
opensuse:python-numpy_1_16_5-gnu-hpc1.16.5-150200.3.5.1 · openSUSE:Leap 15.4Package registry (OSV)
opensuse:python-numpy_1_17_3-gnu-hpc1.17.3-10.1 · openSUSE:Leap 15.3Package registry (OSV)
opensuse:python-numpy11.26.4-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:python2-numpy1.16.5-150200.3.5.1 · openSUSE:Leap 15.3Package registry (OSV)
PyPI:numpy1.10.0Package registry (OSV)
PyPI:numpy1.21Package registry (OSV)
red hat:numpy1:1.17.0-8.el8ost · Red Hat:openstack:16.1::el8Package registry (OSV)
red hat:numpy-debugsource1:1.17.0-8.el8ost · Red Hat:openstack:16.1::el8Package registry (OSV)
red hat:python3-numpy1:1.17.0-8.el8ost · Red Hat:openstack:16.1::el8Package registry (OSV)
red hat:python3-numpy-debuginfo1:1.17.0-8.el8ost · Red Hat:openstack:16.1::el8Package registry (OSV)
red hat:python3-numpy-f2py1:1.17.0-8.el8ost · Red Hat:openstack:16.1::el8Package registry (OSV)
suse:dxflib3.17.0-bp153.2.3.1 · SUSE:Package Hub 15 SP3Package registry (OSV)
suse:python-numpy1.8.0-5.11.1 · SUSE:Linux Enterprise Software Development Kit 12 SP5Package registry (OSV)
suse:python-numpy_1_13_3-gnu-hpc1.13.3-4.12.1 · SUSE:Linux Enterprise Module for HPC 12Package registry (OSV)
suse:python-numpy_1_16_5-gnu-hpc1.16.5-150200.3.5.1 · SUSE:Linux Enterprise Module for HPC 15 SP3Package registry (OSV)
suse:python-numpy_1_17_3-gnu-hpc1.17.3-10.1 · SUSE:Linux Enterprise Real Time 15 SP2Package registry (OSV)
suse:python2-numpy1.16.5-150200.3.5.1 · SUSE:Linux Enterprise Module for Python 2 15 SP3Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Root cause

When data is copied, the source length is not compared with the size of the destination buffer. Excess data overwrites adjacent memory.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
char buf[256];memcpy(buf, pkt->data, pkt->len);

Fixed

c
char buf[256];if (pkt->len > sizeof(buf)) {  return -EINVAL;}memcpy(buf, pkt->data, pkt->len);

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

All records