lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 25 Sep 2014 15:10:08 -0700
From: Seth Arnold <seth.arnold@...onical.com>
To: Paul Vixie <paul@...barn.org>
Cc: fulldisclosure@...lists.org
Subject: Re: [FD] Critical bash vulnerability CVE-2014-6271

On Thu, Sep 25, 2014 at 01:54:31PM -0700, Paul Vixie wrote:
> no. the problem occurs when /bin/sh is bash, or when a network invokable
> script begins with the line #!/bin/bash. it has nothing to do with the
> user's shell. rather, it's the shell used by popen() and system() and of
> course (execl, execlp, execle, execv, execvp, execvpe), or, it's the
> explicitly called shell named at the top of the script itself.

Which systems go through /bin/sh for the exec*() family of functions?

Thanks

Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)


_______________________________________________
Sent through the Full Disclosure mailing list
http://nmap.org/mailman/listinfo/fulldisclosure
Web Archives & RSS: http://seclists.org/fulldisclosure/

Powered by blists - more mailing lists