Local resource exhaustion via settings interpolation
Published Jun 4, 2024 · Updated Mar 13, 2025
Resource exhaustion in Canonical Apport before 2.21.0 allows local users to interrupt crash reporting via a crafted settings file. The get_config() path in apport/fileutils.py enables ConfigParser interpolation while reading ~/.config/apport/settings, allowing recursively referenced values to expand exponentially. A local user must supply the settings file; parsing it consumes CPU and memory in the Apport process, interrupting crash-report generation.
Summary
What happened
Resource exhaustion in Canonical Apport before 2.21.0 allows local users to interrupt crash reporting via a crafted settings file. The get_config() path in apport/fileutils.py enables ConfigParser interpolation while reading ~/.config/apport/settings, allowing recursively referenced values to expand exponentially. A local user must supply the settings file; parsing it consumes CPU and memory in the Apport process, interrupting crash-report generation.
The record
- CVE
- CVE-2022-28652
- Published
- Jun 4, 2024
- Updated
- Mar 13, 2025
- Vendor
- Canonical
- Product
- Apport
- Classifications
- CWE-776, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 4, 2024CVE publishedPublication date reported by the CVE source.
- Mar 13, 2025Record 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 <2.21.0
What conditions does exploitation require?
What is affected?
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