Apport Project
Apport Project Apport: vulnerabilities and CVEs
Apport Project Apport has 24 published vulnerabilities, 0 of them in the last 12 months. 0 are rated critical and 0 are listed by CISA as actively exploited.
CVEs24
Last 12 months0
Critical0
Actively exploited0
All vulnerabilities in the catalogue →⭐ Follow this technology
Latest vulnerabilities
| CVE | Severity | EPSS | Active exploitation | Published | Description |
|---|---|---|---|---|---|
| CVE-2022-28658 | Medium (5.5) | 0.20% | — | Jun 4, 2024 | Apport argument parsing mishandles filename splitting on older kernels resulting in argument spoofing |
| CVE-2022-28657 | High (7.8) | 0.23% | — | Jun 4, 2024 | Apport does not disable python crash handler before entering chroot |
| CVE-2022-28656 | Medium (5.5) | 0.20% | — | Jun 4, 2024 | is_closing_session() allows users to consume RAM in the Apport process |
| CVE-2022-28655 | High (7.1) | 0.21% | — | Jun 4, 2024 | is_closing_session() allows users to create arbitrary tcp dbus connections |
| CVE-2022-28654 | Medium (5.5) | 0.25% | — | Jun 4, 2024 | is_closing_session() allows users to fill up apport.log |
| CVE-2022-28652 | Medium (5.5) | 0.20% | — | Jun 4, 2024 | ~/.config/apport/settings parsing is vulnerable to "billion laughs" attack |
| CVE-2019-15790 | Low (3.3) | 0.52% | — | Apr 28, 2020 | 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… |
| CVE-2020-8833 | Medium (4.7) | 0.34% | — | Apr 22, 2020 | 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… |
| CVE-2020-8831 | Medium (5.5) | 0.65% | — | Apr 22, 2020 | 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… |
| CVE-2019-11485 | Low (3.3) | 0.26% | — | Feb 8, 2020 | Sander Bos discovered Apport's lock file was in a world-writable directory which allowed all users to prevent crash handling. |
| CVE-2019-11483 | Low (3.3) | 0.40% | — | Feb 8, 2020 | 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. |
| CVE-2019-11482 | Medium (4.7) | 0.23% | — | Feb 8, 2020 | 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. |
| CVE-2019-11481 | High (7.8) | 0.45% | — | Feb 8, 2020 | 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,… |
| CVE-2019-7307 | High (7) | 0.33% | — | Aug 29, 2019 | 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… |
| CVE-2018-6552 | High (7.8) | 0.39% | — | May 31, 2018 | 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,… |
| CVE-2017-14180 | High (7.8) | 0.44% | — | Feb 2, 2018 | 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… |
| CVE-2017-14179 | High (7.8) | 0.36% | — | Feb 2, 2018 | 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… |
| CVE-2017-14177 | High (7.8) | 0.39% | — | Feb 2, 2018 | 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… |
| CVE-2017-10708 | High (7.8) | 2.1% | — | Jul 18, 2017 | 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… |
| CVE-2016-9951 | Medium (6.5) | 6.7% | — | Dec 17, 2016 | 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… |
| CVE-2016-9950 | High (7.8) | 6.5% | — | Dec 17, 2016 | An issue was discovered in Apport before 2.20.4. There is a path traversal issue in the Apport crash file "Package" and "SourcePackage" fields. These fields are used to build a path to the package specific hook files in… |
| CVE-2016-9949 | High (7.8) | 18% | — | Dec 17, 2016 | An issue was discovered in Apport before 2.20.4. In apport/ui.py, Apport reads the CrashDB field and it then evaluates the field as Python code if it begins with a "{". This allows remote attackers to execute arbitrary… |
| CVE-2015-1338 | High (7.2) | 0.91% | — | Oct 1, 2015 | kernel_crashdump in Apport before 2.19 allows local users to cause a denial of service (disk consumption) or possibly gain privileges via a (1) symlink or (2) hard link attack on /var/crash/vmcore.log. |
| CVE-2015-1318 | High (7.2) | 4.2% | — | Apr 17, 2015 | The crash reporting feature in Apport 2.13 through 2.17.x before 2.17.1 allows local users to gain privileges via a crafted usr/share/apport/apport file in a namespace (container). |