You joke but at work our security office mass reset passwords because they saw a list of users in the pwd file. Even after others pointed out it was just a list of usernames not their credentials AND that it couldn’t be the actual credentials as we’re an AD shop
Right? And while Linux generally seems to let you shoot yourself in your foot if you’d really like to, things like --no-preserve-root mean they do put SOME guardrails out there. lol. $USER seems worth making immutable. heh
I already found another one!
echo $USERprints my current user name. Once I doUSER=rootit shows im running as root. And I wasn’t even asked for my sudo password! :O :O :Oalias whoami='echo root'That seems like an adjacent vector, want to coop on the CVE?
You joke but at work our security office mass reset passwords because they saw a list of users in the pwd file. Even after others pointed out it was just a list of usernames not their credentials AND that it couldn’t be the actual credentials as we’re an AD shop
They would definitely fall for that 😭
Oh my xD
Huh. It is worth bearing in mind not to trust $USER before doing something based on it, though, if that thing is important.
The interesting thing is that bash allows writing this variable. I would’ve expected it to be readonly for obvious reasons.
USER is just an environment variable in the environment block like any other; even if Bash didn’t allow changing it, any other program could.
Right? And while Linux generally seems to let you shoot yourself in your foot if you’d really like to, things like
--no-preserve-rootmean they do put SOME guardrails out there. lol. $USER seems worth making immutable. hehPwned again!