How not to run a CA

Re:How not to run a CA by flamingcow on Thursday March 01, 2018 @07:05PM (#16497597)

Does it really? Even if the code author hadn't learned to escape/sanitize close to use so it's visible (or to avoid cases where you need to escape/sanitize entirely, like using something that bypasses the shell and takes array arguments), let's look at the manpages.

PHP's system() manpage: http://php.net/manual/en/function.system.php

  [red box]
  Warning
  When allowing user-supplied data to be passed to this function, use escapeshellarg() or escapeshellcmd() to ensure that users cannot trick the system into executing arbitrary commands.

system(3): http://man7.org/linux/man-pages/man3/system.3.html

  Any user input that is employed as part of command should be carefully sanitized, to ensure that unexpected shell commands or command options are not executed.  Such risks are especially grave when using system() from a privileged program.

This is a canonical mistake that's used as a mistake example in textbooks.

[ Parent | on HN ]

Re:How not to run a CA by benmmurphy on Thursday March 01, 2018 @08:53PM (#16498276)

at this point i think the problem with system() should be blamed on the language and not the people using the language. how many legitimate uses of system() functiona call are there. a primitive that does fork() execv() on an array is a much better alternative. yeah, it doesn't 100% fix problems you might have issues with - style flags but you are in a much better situation. like if your users want to do system() maybe force them to do the extra work.

system() style functionality -> should be the hard thing to do execv() style functionality() -> should be the easy thing to do

[ Parent | on HN ]

Re:How not to run a CA by technion on Friday March 02, 2018 @04:10AM (#16500118)

Whilst I do wish I could cleanse a web application of actually supporting system(), we have system() in Perl, Ruby, Python, and modules for Node. I've seen people bagging PHP and that really isn't fair.

Shower thought: Allow me to globally disable system() in for language x. Aside from the obvious case of just banning these insane system calls, you're protected against surprise vectors in parsers.

Edit: You would presumably mitigate pipe open vulnerabilities too

[ Parent | on HN ]

Re:How not to run a CA by tetha on Friday March 02, 2018 @09:08AM (#16501419)

You can do so with SELinux btw. You can remove the right for a program to run the exec syscall.

It's just sad that there is no really good tutorial how to write your own SELinux modules for your own applications. It's easier than it seems and allows some really powerful security measures.

[ Parent | on HN ]

Re:How not to run a CA by hultner on Friday March 02, 2018 @06:24PM (#16506689)

Maybe you could write one? I bet that it would be really appreciated.

[ Parent | on HN ]

Re:How not to run a CA by eequah9L on Friday March 02, 2018 @05:05AM (#16500320)

I suspect that these languages just end up deferring to the system() library function in libc. LD_PRELOAD or other linker trick would then let you override it with a do-nothing or complain-loudly replacement.

[ Parent | on HN ]

Re:How not to run a CA by __david__ on Friday March 02, 2018 @12:33PM (#16503711)

All of those languages have an option to pass in arguments as an array and bypass the shell completely. PHP does not. It's much safer with no shell (though not perfect).

[ Parent | on HN ]