News for hackers. Stuff that matters.
Re:How not to run a CA by jiggliemon on Thursday March 01, 2018 @11:18AM (#16493211)
Oh my. There must be some sort of hall of fame for security vulnerabilities. And this belongs in it.

Perhaps they’re passing this command to a secured container? I shouldn’t make excuses for them, but passing root commands to the shell seems too far out there.

Re:How not to run a CA by zbentley on Thursday March 01, 2018 @12:13PM (#16493888)
> root commands to the shell seems too far out there

You haven't been in software too long, have ya? /s

Glibness aside (and I meant the above as a joke, not a personal attack), this is distressingly common to the point of being near-universal in some areas of our industry.

Re:How not to run a CA by profmonocle on Thursday March 01, 2018 @01:21PM (#16494592)
> Perhaps they’re passing this command to a secured container?

That would indicate they were concerned about shell injection while writing the code. But if that were true, why would they skip the much simpler step of sanitizing/escaping the input?

Re:How not to run a CA by cyphar on Saturday March 03, 2018 @08:15PM (#16512738)
> Perhaps they’re passing this command to a secured container?

This would still raise my eyebrows, since root inside a container is still something you should avoid unless absolutely necessary (especially if they aren't using user namespaces). Just because containers add some newer security features to regular processes doesn't mean you should forget the security features (POSIX DAC) that were there in the first place.

Re:How not to run a CA by peterwwillis on Thursday March 01, 2018 @07:29PM (#16497735)
> There must be some sort of hall of fame for security vulnerabilities.

It's called the Pwnie Awards.

https://pwnies.com/

Re:How not to run a CA by chopin on Thursday March 01, 2018 @04:49PM (#16496701)
This seems more to warrant a business Darwin Award.