本ページは apport_project apport に影響する公開済み CVE（NVD の CPE 経由で関連付け）を列挙します。各行に深刻度指標・概要・公開日が含まれます。
| CVE | 概要 | ソース | CVSS 最大値 | EPSS（%） | 公開 | 更新 |
|---|---|---|---|---|---|---|
| CVE-2022-28658 | Apport argument parsing mishandles filename splitting on older kernels resulting in argument spoofing | [email protected] | 5.5 | 0.04% | 2024-06-04 | 2024-11-21 |
| CVE-2022-28657 | Apport does not disable python crash handler before entering chroot | [email protected] | 7.8 | 0.05% | 2024-06-04 | 2024-11-21 |
| CVE-2022-28656 | is_closing_session() allows users to consume RAM in the Apport process | [email protected] | 5.5 | 0.04% | 2024-06-04 | 2025-03-19 |
| CVE-2022-28655 | is_closing_session() allows users to create arbitrary tcp dbus connections | [email protected] | 7.1 | 0.04% | 2024-06-04 | 2024-11-21 |
| CVE-2022-28654 | is_closing_session() allows users to fill up apport.log | [email protected] | 5.5 | 0.04% | 2024-06-04 | 2024-11-21 |
| CVE-2022-28652 | ~/.config/apport/settings parsing is vulnerable to "billion laughs" attack | [email protected] | 5.5 | 0.04% | 2024-06-04 | 2025-03-13 |
| CVE-2019-15790 | Apport reads and writes information on a crashed process to /proc/pid with elevated privileges. Apport then determines which user the crashed process belongs to by reading /proc/pid through get_pid_info() in data/apport. An unprivileged user could exploit this to read information about a privileged running process by exploiting PID recycling. This information could then be used to obtain ASLR offsets for a process with an existing memory corruption vulnerability. The initial fix introduced regre | [email protected] | 2.8 | 0.06% | 2020-04-28 | 2025-11-03 |
| CVE-2020-8833 | Time-of-check Time-of-use Race Condition vulnerability on crash report ownership change in Apport allows for a possible privilege escalation opportunity. If fs.protected_symlinks is disabled, this can be exploited between the os.open and os.chown calls when the Apport cron script clears out crash files of size 0. A symlink with the same name as the deleted file can then be created upon which chown will be called, changing the file owner to root. Fixed in versions 2.20.1-0ubuntu2.23, 2.20.9-0ubun | [email protected] | 5.6 | 0.04% | 2020-04-22 | 2024-11-21 |
| CVE-2020-8831 | Apport creates a world writable lock file with root ownership in the world writable /var/lock/apport directory. If the apport/ directory does not exist (this is not uncommon as /var/lock is a tmpfs), it will create the directory, otherwise it will simply continue execution using the existing directory. This allows for a symlink attack if an attacker were to create a symlink at /var/lock/apport, changing apport's lock file location. This file could then be used to escalate privileges, for example | [email protected] | 6.5 | 0.10% | 2020-04-22 | 2024-11-21 |
| CVE-2019-11485 | Sander Bos discovered Apport's lock file was in a world-writable directory which allowed all users to prevent crash handling. | [email protected] | 3.3 | 0.09% | 2020-02-08 | 2024-11-21 |
| CVE-2019-11483 | Sander Bos discovered Apport mishandled crash dumps originating from containers. This could be used by a local attacker to generate a crash report for a privileged process that is readable by an unprivileged user. | [email protected] | 7.0 | 0.12% | 2020-02-08 | 2025-11-03 |
| CVE-2019-11482 | Sander Bos discovered a time of check to time of use (TOCTTOU) vulnerability in apport that allowed a user to cause core files to be written in arbitrary directories. | [email protected] | 4.2 | 0.09% | 2020-02-08 | 2024-11-21 |
| CVE-2019-11481 | Kevin Backhouse discovered that apport would read a user-supplied configuration file with elevated privileges. By replacing the file with a symbolic link, a user could get apport to read any file on the system as root, with unknown consequences. | [email protected] | 3.8 | 0.19% | 2020-02-08 | 2024-11-21 |
| CVE-2019-7307 | Apport before versions 2.14.1-0ubuntu3.29+esm1, 2.20.1-0ubuntu2.19, 2.20.9-0ubuntu7.7, 2.20.10-0ubuntu27.1, 2.20.11-0ubuntu5 contained a TOCTTOU vulnerability when reading the users ~/.apport-ignore.xml file, which allows a local attacker to replace this file with a symlink to any other file on the system and so cause Apport to include the contents of this other file in the resulting crash report. The crash report could then be read by that user either by causing it to be uploaded and reported t | [email protected] | 7.0 | 0.10% | 2019-08-29 | 2024-11-21 |
| CVE-2018-6552 | Apport does not properly handle crashes originating from a PID namespace allowing local users to create certain files as root which an attacker could leverage to perform a denial of service via resource exhaustion, possibly gain root privileges, or escape from containers. The is_same_ns() function returns True when /proc/<global pid>/ does not exist in order to indicate that the crash should be handled in the global namespace rather than inside of a container. However, the portion of the data/ap | [email protected] | 7.8 | 0.04% | 2018-05-31 | 2024-11-21 |
| CVE-2017-14180 | Apport 2.13 through 2.20.7 does not properly handle crashes originating from a PID namespace allowing local users to create certain files as root which an attacker could leverage to perform a denial of service via resource exhaustion or possibly gain root privileges, a different vulnerability than CVE-2017-14179. | [email protected] | 7.8 | 0.05% | 2018-02-02 | 2025-11-03 |
| CVE-2017-14179 | Apport before 2.13 does not properly handle crashes originating from a PID namespace allowing local users to create certain files as root which an attacker could leverage to perform a denial of service via resource exhaustion, possibly gain root privileges, or escape from containers. | [email protected] | 7.8 | 0.04% | 2018-02-02 | 2024-11-21 |
| CVE-2017-14177 | Apport through 2.20.7 does not properly handle core dumps from setuid binaries allowing local users to create certain files as root which an attacker could leverage to perform a denial of service via resource exhaustion or possibly gain root privileges. NOTE: this vulnerability exists because of an incomplete fix for CVE-2015-1324. | [email protected] | 7.8 | 0.05% | 2018-02-02 | 2024-11-21 |
| CVE-2017-10708 | An issue was discovered in Apport through 2.20.x. In apport/report.py, Apport sets the ExecutablePath field and it then uses the path to run package specific hooks without protecting against path traversal. This allows remote attackers to execute arbitrary code via a crafted .crash file. | [email protected] | 7.8 | 0.78% | 2017-07-18 | 2026-05-13 |
| CVE-2016-9951 | An issue was discovered in Apport before 2.20.4. A malicious Apport crash file can contain a restart command in `RespawnCommand` or `ProcCmdline` fields. This command will be executed if a user clicks the Relaunch button on the Apport prompt from the malicious crash file. The fix is to only show the Relaunch button on Apport crash files generated by local systems. The Relaunch button will be hidden when crash files are opened directly in Apport-GTK. | [email protected] | 6.5 | 7.94% | 2016-12-17 | 2026-05-06 |