full-disclosure - THREATCON HITTING DANGEROUS LEVELS!

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]

Message-ID: <20020930074000.A246@dw>
From: full-disclosure at botanicus.net (Dave Wilson)
Subject: THREATCON HITTING DANGEROUS LEVELS!

On Sun, Sep 29, 2002 at 10:03:36PM -0700, silvio@....net.au wrote:

> #include <stdio.h>
> int main(int argc, char *argv[]) { char *v[] = { NULL };
> execve(argv[1], v, NULL); }

This is the linux glibc bootstrap code behaviour. main() is never
reached. It's not new either.

> This is of course, not really a security threat by any means.. It is an
> annoying bug that effects alot of things and is really not handled
> correctly in the majority of implementations.

How about not misusing exec()?  'course not, let's patch our kernels to
stop idiots from using exec()!!