Local code execution via retained Python crash handler
Published Jun 4, 2024 · Updated Aug 3, 2024
Code execution in the container crash path in Canonical Apport before 2.21.0 allows local users to execute arbitrary code. The path enters a container chroot without first disabling Apport's Python crash handler, leaving that handler active inside the changed root. Exploitation requires local low-privilege access and a container crash processed through the affected chroot path.
Summary
What happened
Code execution in the container crash path in Canonical Apport before 2.21.0 allows local users to execute arbitrary code. The path enters a container chroot without first disabling Apport's Python crash handler, leaving that handler active inside the changed root. Exploitation requires local low-privilege access and a container crash processed through the affected chroot path.
The record
- CVE
- CVE-2022-28657
- Published
- Jun 4, 2024
- Updated
- Aug 3, 2024
- Vendor
- Canonical
- Product
- Apport
- Classifications
- CWE-400, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 4, 2024CVE 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?
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