Process interruption via oversized struct format string
Published Aug 22, 2023 · Updated Aug 3, 2024
Resource exhaustion in affected Python 3 plistlib releases allows attackers to cause a service interrupt with a malformed binary plist. The read_ints function repeats an input-controlled count in a struct.unpack format string, creating an enormous string that consumes CPU and memory. Exploitation requires an application or user to parse the crafted file; the resulting exhaustion interrupts that Python process without reported confidentiality or integrity impact.
Summary
What happened
Resource exhaustion in affected Python 3 plistlib releases allows attackers to cause a service interrupt with a malformed binary plist. The read_ints function repeats an input-controlled count in a struct.unpack format string, creating an enormous string that consumes CPU and memory. Exploitation requires an application or user to parse the crafted file; the resulting exhaustion interrupts that Python process without reported confidentiality or integrity impact.
The record
- CVE
- CVE-2022-48564
- Published
- Aug 22, 2023
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-400, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 22, 2023CVE publishedPublication date reported by the CVE source.
- Aug 3, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- Malformed binary plist proof of conceptproof of concept · demonstrated
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