read_ints in plistlib.py in Python through 3.9.1 is vulnerable to a potential DoS attack via CPU and RAM exhaustion when processing malforme
Noroxi assessment
Priority: Monitor (action score 26/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.6% (FIRST EPSS); higher than 76.3% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: platform-python (AlmaLinux:8) 3.6.8-56.el8_9.2.alma.1; platform-python-debug (AlmaLinux:8) 3.6.8-56.el8_9.2.alma.1; platform-python-devel (AlmaLinux:8) 3.6.8-56.el8_9.2.alma.1.
Low priority for now. Upgrade to platform-python (AlmaLinux:8) 3.6.8-56.el8_9.2.alma.1; platform-python-debug (AlmaLinux:8) 3.6.8-56.el8_9.2.alma.1; platform-python-devel (AlmaLinux:8) 3.6.8-56.el8_9.2.alma.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
read_ints in plistlib.py in Python through 3.9.1 is vulnerable to a potential DoS attack via CPU and RAM exhaustion when processing malformed Apple Property List files in binary format.
- Published
- Aug 22, 2023
- Updated
- Jun 17, 2026
- EPSS
- 1.6% · 76th percentile
- CWE
- CWE-400
Report tools
Action score
26
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.6%
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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| python | python | cpe:2.3:a:python:python |
| netapp | active iq unified manager | cpe:2.3:a:netapp:active_iq_unified_manager |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- netapp active iq unified managerall versions
- python pythonbefore 3.6.13
- python python3.7.0 and later · before 3.7.10
- python python3.8.0 and later · before 3.8.7
- python python3.9.0 and later · before 3.9.1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | platform-python | before 3.6.8-56.el8_9.2.alma.1 | 3.6.8-56.el8_9.2.alma.1 |
| AlmaLinux:8 | platform-python-debug | before 3.6.8-56.el8_9.2.alma.1 | 3.6.8-56.el8_9.2.alma.1 |
| AlmaLinux:8 | platform-python-devel | before 3.6.8-56.el8_9.2.alma.1 | 3.6.8-56.el8_9.2.alma.1 |
| AlmaLinux:8 | python3-idle | before 3.6.8-56.el8_9.2.alma.1 | 3.6.8-56.el8_9.2.alma.1 |
| AlmaLinux:8 | python3-libs | before 3.6.8-56.el8_9.2.alma.1 | 3.6.8-56.el8_9.2.alma.1 |
| AlmaLinux:8 | python3-test | before 3.6.8-56.el8_9.2.alma.1 | 3.6.8-56.el8_9.2.alma.1 |
| AlmaLinux:8 | python3-tkinter | before 3.6.8-56.el8_9.2.alma.1 | 3.6.8-56.el8_9.2.alma.1 |
| Debian:10 | python3.7 | before 3.7.3-2+deb10u6 | 3.7.3-2+deb10u6 |
| Debian:12 | pypy3 | before 7.3.5+dfsg-2 | 7.3.5+dfsg-2 |
| Red Hat:enterprise_linux:8::appstream | platform-python | before 0:3.6.8-56.el8_9.2 | 0:3.6.8-56.el8_9.2 |
| Red Hat:enterprise_linux:8::appstream | platform-python-debug | before 0:3.6.8-56.el8_9.2 | 0:3.6.8-56.el8_9.2 |
| Red Hat:enterprise_linux:8::appstream | platform-python-devel | before 0:3.6.8-56.el8_9.2 | 0:3.6.8-56.el8_9.2 |
| Red Hat:enterprise_linux:8::appstream | python3-debuginfo | before 0:3.6.8-56.el8_9.2 | 0:3.6.8-56.el8_9.2 |
| Red Hat:enterprise_linux:8::appstream | python3-debugsource | before 0:3.6.8-56.el8_9.2 | 0:3.6.8-56.el8_9.2 |
| Red Hat:enterprise_linux:8::appstream | python3-idle | before 0:3.6.8-56.el8_9.2 | 0:3.6.8-56.el8_9.2 |
| Red Hat:enterprise_linux:8::appstream | python3-test | before 0:3.6.8-56.el8_9.2 | 0:3.6.8-56.el8_9.2 |
| Red Hat:enterprise_linux:8::appstream | python3-tkinter | before 0:3.6.8-56.el8_9.2 | 0:3.6.8-56.el8_9.2 |
| Red Hat:enterprise_linux:8::baseos | python3 | before 0:3.6.8-56.el8_9.2 | 0:3.6.8-56.el8_9.2 |
| Red Hat:enterprise_linux:8::baseos | python3-libs | before 0:3.6.8-56.el8_9.2 | 0:3.6.8-56.el8_9.2 |
| Red Hat:rhel_eus:8.6::appstream | platform-python | before 0:3.6.8-47.el8_6.4 | 0:3.6.8-47.el8_6.4 |
| Red Hat:rhel_eus:8.6::appstream | platform-python-debug | before 0:3.6.8-47.el8_6.4 | 0:3.6.8-47.el8_6.4 |
| Red Hat:rhel_eus:8.6::appstream | platform-python-devel | before 0:3.6.8-47.el8_6.4 | 0:3.6.8-47.el8_6.4 |
| Red Hat:rhel_eus:8.6::appstream | python3-debuginfo | before 0:3.6.8-47.el8_6.4 | 0:3.6.8-47.el8_6.4 |
| Red Hat:rhel_eus:8.6::appstream | python3-debugsource | before 0:3.6.8-47.el8_6.4 | 0:3.6.8-47.el8_6.4 |
+15
Same product
python: all recordsOther highest-scoring records for the same primary product.
- CVE-2016-5636Integer overflow in the get_data function in zipimport.c in CPython (aka Python) before 2.7.12, 3.x before 3.4.5, and 3.5.x before 3.5.2 all47Plan
- CVE-2007-4559Directory traversal vulnerability in the (1) extract and (2) extractall functions in the tarfile module in Python allows user-assisted remot47Plan
- CVE-2021-3177Python 3.x through 3.9.1 has a buffer overflow in PyCArg_repr in _ctypes/callproc.c, which may lead to remote code execution in certain Pyth46Plan
Published before and after this one in the same product
- ← EarlierCVE-2023-36632Jun 25, 2023 · The legacy email.utils.parseaddr function in Python through 3.11.4 allows attackers to trigger "RecursionError: maximum recursion depth exce30Monitor
- ← EarlierCVE-2023-38898Aug 15, 2023 · An issue in Python cpython v.3.7 allows an attacker to obtain sensitive information via the _asyncio._swap_current_task component.22Monitor
- Later →CVE-2022-48565Aug 22, 2023 · An XML External Entity (XXE) issue was discovered in Python through 3.9.1.41Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| almalinux:platform-python | 3.6.8-56.el8_9.2.alma.1 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:platform-python-debug | 3.6.8-56.el8_9.2.alma.1 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:platform-python-devel | 3.6.8-56.el8_9.2.alma.1 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:python3-idle | 3.6.8-56.el8_9.2.alma.1 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:python3-libs | 3.6.8-56.el8_9.2.alma.1 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:python3-test | 3.6.8-56.el8_9.2.alma.1 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:python3-tkinter | 3.6.8-56.el8_9.2.alma.1 · AlmaLinux:8 | Package registry (OSV) |
| debian:pypy3 | 7.3.5+dfsg-2 · Debian:12 | Package registry (OSV) |
| debian:python3.7 | 3.7.3-2+deb10u6 · Debian:10 | Package registry (OSV) |
| red hat:platform-python | 0:3.6.8-56.el8_9.2 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:platform-python-debug | 0:3.6.8-56.el8_9.2 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:platform-python-devel | 0:3.6.8-56.el8_9.2 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:python3 | 0:3.6.8-56.el8_9.2 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:python3-debuginfo | 0:3.6.8-56.el8_9.2 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:python3-debugsource | 0:3.6.8-56.el8_9.2 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:python3-idle | 0:3.6.8-56.el8_9.2 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:python3-libs | 0:3.6.8-56.el8_9.2 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:python3-test | 0:3.6.8-56.el8_9.2 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:python3-tkinter | 0:3.6.8-56.el8_9.2 · Red Hat:enterprise_linux:8::appstream | Package 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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.
Credits
All researchersFinders, 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.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-400 · Uncontrolled Resource ConsumptionCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
nvd-primary
Root cause
Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.
The bug in code
The whole CWE-400 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
function expand(node) {
return node.children.map(expand);
}Fixed
const MAX_DEPTH = 32;
function expand(node, depth = 0) {
if (depth > MAX_DEPTH) throw new Error("too deep");
return node.children.map((c) => expand(c, depth + 1));
}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.