Skip to content
Fencer Vulns
critical 9.8

CVE-2023-29824 json

Withdrawn: Use after free in SciPy

published 2023-07-06 3 y ago modified 2026-06-17 4 mo ago also GHSA-jrfm-2h82-xg28 , PYSEC-2023-114 , EUVD-2023-0235

cvss
9.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.3%
EPSS 1.3% chance of exploitation in 30 days, percentile 71%
public exploits
0
none known

Summary

A use-after-free issue was discovered in Py_FindObjects() function in SciPy versions prior to 1.8.0. NOTE: the vendor and discoverer indicate that this is not a security issue.

Patch / fix

  • pypi scipy 1.8.0
  • scipy scipy 1.8.0
  • scipy Debian 14, Debian 13, Debian 12 1.8.1-3

debian advisories DEBIAN-CVE-2023-29824

  • fmt openshift 4.14 9.1.0-1.el9
  • crun openshift 4.14 1.9.2-1.rhaos4.14.el8
  • crun openshift 4.14 1.9.2-1.rhaos4.14.el9
  • perf openshift 4.14 5.14.0-284.36.1.el9_2
  • rtla openshift 4.14 5.14.0-284.36.1.el9_2
  • runc openshift 4.14 4:1.1.9-2.1.rhaos4.14.el8
  • runc openshift 4.14 4:1.1.9-2.1.rhaos4.14.el9
  • catch openshift 4.14 3.3.2-1.el9

red hat advisories RHSA-2023:5009

  • python-scipy SLE Module for Package Hub 15 SP5, SLE Module for Package Hub 15 SP4, openSUSE Leap 15.5 +1 more 1.3.3-150200.5.3.1
  • python-scipy_1_3_3-gnu-hpc SLE Module for Package Hub 15 SP5, SLE Module for HPC 15 SP5, SLE Module for HPC 15 SP4 +2 more 1.3.3-150200.5.3.1
  • python-scipy openSUSE Leap 15.4 1.2.0-150100.4.6.1
  • python-scipy_1_2_0-gnu-hpc openSUSE Leap 15.5, openSUSE Leap 15.4 1.2.0-150100.4.6.1

suse advisories SUSE-SU-2023:3272-1SUSE-SU-2023:2970-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2023-29824 updated cvss 7.0

scipy: use-after-free in Py_FindObjects() function

  • Red Hat Enterprise Linux 6 scipy Red Hat Enterprise Linux 7 scipy
    affected: no fix planned “Out of support scope”
  • Red Hat Enterprise Linux 8 scipy, python2-scipy, python3-scipy, python38-scipy, python39-scipy Red Hat Enterprise Linux 9 python3-scipy, python3.11-scipy Red Hat Software Collections rh-python38-python-scipy
    affected: no fix planned “Will not fix”
  • Red Hat OpenShift Container Platform 4.14 google-benchmark 1.8.2-1.el9
    fixed: vendor fix RHSA-2023:5009
  • Red Hat Ironic content for Red Hat OpenShift Container Platform 4.14 python-pbr 5.11.1-0.1.el9, python-wrapt 1.14.1-1.el9, python3-pbr 5.11.1-0.1.el9, python3-wrapt 1.14.1-1.el9, python-fixtures 4.0.1-1.el9, python-tenacity 6.3.1-1.el9, +135 more Red Hat Enterprise Linux 8 python3.11-scipy Red Hat OpenShift Container Platform 4 python-sortedcontainers Red Hat OpenShift Container Platform 4.14 fmt 9.1.0-1.el9, catch 3.3.2-1.el9, gmock 1.13.0-1.el9, gtest 1.13.0-1.el9, cri-tools 1.27.0-2.1.el8, cri-tools 1.27.0-2.1.el9, +154 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
total
Assessed
2 y ago

Exploit prediction

1.33% chance of exploitation in the next 30 days, higher than 71% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/scipy/scipy/issues/14713 referenced PoC, tagged "exploit" by a source, unverified
  • github.com https://github.com/scipy/scipy/issues/14713#issuecomment-1629468565 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CISA ADP 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
pypi scipy
<1.8.0
1.8.0

Affected products

  • scipy scipy

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.