full-disclosure - bash vulnerability?

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: <20050816172318.BCB891104F@kris.7deadly.org>
Date: Tue Aug 16 18:23:26 2005
From: greed at pobox.com (Graham Reed)
Subject: bash vulnerability?

Rik Bobbaers writes: 

> so ctrl-c is just a SIGINT... you can make the program ignore that signal, i 
> don't want to start doing that in asm (because its just a poc) but just 
> change the pointer to the signal handler to rewrite the pointer to a return 
> statement or something... 

Set SIGINT's sa_handler to SIG_IGN.  No need to make an actual handler. 

But, Linux seems to be particularly susceptible to fork-bombs.  Other 
systems (AIX, Solaris, BSD) I have accidentally (and later deliberately) 
fork-bombed have been easier to recover from console ^C.  Linux tends to 
lose keyboard processing completely, so you can't get a ^C in edgewise.  (At 
least, based on various Red Hats.)