Design flaws in issetugid()

jerm · August 4, 2026, 7:16am

gist.github.com

https://gist.github.com/nicowilliams/4daf74a3a0c86848d3cbd9d0cdb5e26e

issetugid-sadness.md

*Warning: work in progress.  Incomplete*

People who have been in security a long time (or even not that long) know that some inputs should be treated
as tainted.  For example, environment variables from a user should not be used in a
set-uid program, inputs from a different user should be validated, etc...
Traditionally we say that the environment of a set-uid program is *`tainted`* and
should not be used (or used with much care).

Therefore we want all set-uid/set-gid programs to treat their environment and user
inputs as tainted.

This file has been truncated. show original

Topic		Replies	Views
Linux config for privacy [beginner questions] Questions please-eli5	12	1402	February 9, 2026
Madaidens Security Machine ID question - Linux hardening General	4	904	February 12, 2024
KEY-ID \| FIDO security keys General	2	591	October 8, 2023
Many Password Managers Don't Properly Support Passkeys General	11	529	May 5, 2026
Women Dating Safety App 'Tea' Breached, Users' IDs Posted to 4chan News article , software	15	1928	October 22, 2025

Design flaws in issetugid()

Related topics