Show filters
24 Total Results
Displaying 1-10 of 24
Sort by:
Attacker Value
Unknown
CVE-2022-28658
Disclosure Date: June 04, 2024 (last updated June 12, 2024)
Apport argument parsing mishandles filename splitting on older kernels resulting in argument spoofing
0
Attacker Value
Unknown
CVE-2022-28657
Disclosure Date: June 04, 2024 (last updated June 12, 2024)
Apport does not disable python crash handler before entering chroot
0
Attacker Value
Unknown
CVE-2022-28656
Disclosure Date: June 04, 2024 (last updated June 12, 2024)
is_closing_session() allows users to consume RAM in the Apport process
0
Attacker Value
Unknown
CVE-2022-28655
Disclosure Date: June 04, 2024 (last updated June 12, 2024)
is_closing_session() allows users to create arbitrary tcp dbus connections
0
Attacker Value
Unknown
CVE-2022-28654
Disclosure Date: June 04, 2024 (last updated June 12, 2024)
is_closing_session() allows users to fill up apport.log
0
Attacker Value
Unknown
CVE-2022-28652
Disclosure Date: June 04, 2024 (last updated June 12, 2024)
~/.config/apport/settings parsing is vulnerable to "billion laughs" attack
0
Attacker Value
Unknown
CVE-2020-8831
Disclosure Date: April 02, 2020 (last updated February 21, 2025)
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. Fixed in versions 2.20.1-0ubuntu2.23, 2.20.9-0ubuntu7.14, 2.20.11-0ubuntu8.8 and 2.20.11-0ubuntu22.
0
Attacker Value
Unknown
CVE-2020-8833
Disclosure Date: April 02, 2020 (last updated February 21, 2025)
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-0ubuntu7.14, 2.20.11-0ubuntu8.8 and 2.20.11-0ubuntu22.
0
Attacker Value
Unknown
CVE-2019-15790
Disclosure Date: October 30, 2019 (last updated February 21, 2025)
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 regressions in the Python Apport library due to a missing argument in Report.add_proc_environ in apport/report.py. It also caused an autopkgtest failure when reading /proc/pid and with Python 2 compatibility by reading /proc maps. The initial and subsequent regression fixes are in 2.20.11-0ubuntu16, 2.20.11-0ubuntu8.6, 2.20.9-0ubuntu7.12, 2.20.1-0ubuntu2.22 and 2.14.1-0ubuntu3.29+esm3.
0
Attacker Value
Unknown
CVE-2019-11483
Disclosure Date: October 29, 2019 (last updated November 27, 2024)
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.
0