Memory exhaustion via unreleased tuple reference
Published Jul 5, 2023 · Updated Aug 2, 2024
Missing reference release in Py_FindObjects in SciPy before 1.10.0 allows local users to exhaust memory and interrupt a process. When allocation of start or end fails, the error path exits without decrementing the newly created tuple object's reference count, retaining memory. The report requires local code execution that reaches this allocation-failure path, and SciPy disputes security impact because the library is not designed for direct exposure to untrusted users or data.
Summary
What happened
Missing reference release in Py_FindObjects in SciPy before 1.10.0 allows local users to exhaust memory and interrupt a process. When allocation of start or end fails, the error path exits without decrementing the newly created tuple object's reference count, retaining memory. The report requires local code execution that reaches this allocation-failure path, and SciPy disputes security impact because the library is not designed for direct exposure to untrusted users or data.
The record
- CVE
- CVE-2023-25399
- Published
- Jul 5, 2023
- Updated
- Aug 2, 2024
- Vendor
- SciPy
- Product
- SciPy
- Classifications
- CWE-401
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 5, 2023CVE publishedPublication date reported by the CVE source.
- Aug 2, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.10.0
What conditions does exploitation require?
What is affected?
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