execing curl with –output flag to /tmp makes exploit download and later on compile successfully

Sure, but you could just do that in your regular code, no?

Sometimes, setting a wildcard/match on specific lines should also be a good thing to do (ala cat /etc/passwd etc.).

1. /etc/passwd isn’t very meaningful

2. that sort of protection doesn’t fix

   A=“wd” B=“pass” C=”/etc/” cat “$C$B$A

but also 3. you’re running as root already, and can cat shadow: https://bash.rocks/OJ5oO3

however note that lastlog has nobody ever having logged in before.

Finally note that jpm1’s dmesg output is obviously a joke output :)

but writing to /tmp is not, therefore execing curl with –output flag to /tmp makes exploit download and later on compile successfully.

‘noexec’ mountpoints mostly fix this.

it’s running in a cloud container and tmpfs only lives in memory.

so far all requestors of ‘rm -rf /’ are stuck :p