9 results · Feed
-
High 7.8
Local root exploit via `logfile_reopen()` in screen 5.0.0 with setuid-root bit set
Screen 5.0.0 when it runs with setuid-root privileges does not drop privileges while operating on a user supplied path. This allows unprivileged users to create files in arbitrary locations with `root` ownership, the invoking user's (real) group ownership and…
-
Medium 6.0
Temporary chown() of users' TTY to mode 0666 allows PTY hijacking in screen
For a short time they PTY is set to mode 666, allowing any user on the system to connect to the screen session.
-
Medium 5.0
Screen creates by default world-writable PTYs
The default mode of pseudo terminals (PTYs) allocated by Screen was changed from 0620 to 0622, thereby allowing anyone to write to any Screen PTYs in the system.
-
Low 3.3
Screen 5.0.0 and older versions allow file existence tests when installed setuid-root
A minor information leak when running Screen with setuid-root privileges allows unprivileged users to deduce information about a path that would otherwise not be available. Affected are older Screen versions, as well as version 5.0.0.
-
Medium 5.5
Screen has a TOCTOU race potentially allowing to send SIGHUP, SIGCONT to privileged processes when installed setuid-root
Screen version 5.0.0 and older version 4 releases have a TOCTOU race potentially allowing to send SIGHUP, SIGCONT to privileged processes when installed setuid-root.
-
Medium 6.5CVE-2023-24626 Public exploit
socket.c in GNU Screen through 4.9.0, when installed setuid or setgid (the default on platforms such as Arch Linux and …
-
Unscored —
encoding.c in GNU Screen through 4.8.0 allows remote attackers to cause a denial of service (invalid write access and a…
-
Unscored —
A buffer overflow was found in the way GNU Screen before 4.8.0 treated the special escape OSC 49. Specially crafted out…
-
Unscored —
GNU screen before 4.5.1 allows local users to modify arbitrary files and consequently gain root privileges by leveragin…