diff options
| author | Alois Wohlschlager <alois1@gmx-topmail.de> | 2024-02-01 18:42:56 +0100 |
|---|---|---|
| committer | Alois Wohlschlager <alois1@gmx-topmail.de> | 2024-02-03 18:10:50 +0100 |
| commit | f7d21be1d3aae0c4b1e32145b57cb50f4d965850 (patch) | |
| tree | a5251add6ea970c9c2fc4d5f4ef2d8ead4a22dc8 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch | |
| parent | 4f301350dacb4eb0a93578ef3b07c8a996c777e7 (diff) | |
nixos/wrapper: pass trusted argv[0] to the privileged executable
Vulnerabilities caused by argv[0] mishandling in privileged code keep coming
up, recently CVE-2021-4034 in polkit and CVE-2023-6246 in glibc. On the other
hand, legitimate handling of argv[0] is mostly limited to logging and
multiplexing different functionality depending on the basename of the link (an
example for the latter is sudo/sudoedit).
On NixOS, by far the most common source of untrusted argv[0] to privileged
processes should be the wrapper, and it is not used for multiplexing (separate
wrappers are used instead). So we always pass the path of the wrapped program
as argv[0]. Obsolete mitigations for older argv[0]-based issues are deleted.
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions
