Local disk exhaustion via unbounded D-Bus output
Published Jun 4, 2024 · Updated Oct 27, 2024
Resource exhaustion in Canonical Apport before 2.21.0 allows local users to fill apport.log through a crashing process environment. is_closing_session() passes an untrusted DBUS_SESSION_BUS_ADDRESS to gdbus, captures unlimited output, and copies errors into the log. A low-privileged user must trigger Apport on a crashing process and control its environment; repeated output can exhaust disk space and interrupt services.
Summary
What happened
Resource exhaustion in Canonical Apport before 2.21.0 allows local users to fill apport.log through a crashing process environment. is_closing_session() passes an untrusted DBUS_SESSION_BUS_ADDRESS to gdbus, captures unlimited output, and copies errors into the log. A low-privileged user must trigger Apport on a crashing process and control its environment; repeated output can exhaust disk space and interrupt services.
The record
- CVE
- CVE-2022-28654
- Published
- Jun 4, 2024
- Updated
- Oct 27, 2024
- Vendor
- Canonical
- Product
- Apport
- Classifications
- CWE-770, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 4, 2024CVE publishedPublication date reported by the CVE source.
- Oct 27, 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 <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