Compiling the exploit: http://packetstorm.securify.com/9908-exploits/portmap.txt mentioned in #21183 causes gcc internal error: --- ortmap.c:1: parse error before `:' In file included from /usr/include/bits/types.h:166, from /usr/include/stdio.h:41, from portmap.c:46: /usr/include/bits/pthreadtypes.h:48: parse error before `size_t' /usr/include/bits/pthreadtypes.h:48: warning: no semicolon at end of struct or union /usr/include/bits/pthreadtypes.h:51: parse error before `__stacksize' /usr/include/bits/pthreadtypes.h:51: warning: data definition has no type or storage class /usr/include/bits/pthreadtypes.h:52: warning: data definition has no type or storage class In file included from /usr/include/_G_config.h:45, from /usr/include/libio.h:31, from /usr/include/stdio.h:70, from portmap.c:46: /usr/include/gconv.h:71: parse error before `size_t' /usr/include/gconv.h:84: parse error before `size_t' /usr/include/gconv.h:93: parse error before `size_t' /usr/include/gconv.h:169: parse error before `size_t' /usr/include/gconv.h:169: warning: no semicolon at end of struct or union /usr/include/gconv.h:172: parse error before `}' /usr/include/gconv.h:172: warning: data definition has no type or storage class In file included from /usr/include/libio.h:31, from /usr/include/stdio.h:70, from portmap.c:46: /usr/include/_G_config.h:47: field `__cd' has incomplete type /usr/include/_G_config.h:50: field `__cd' has incomplete type /usr/include/_G_config.h:53: Internal error: Segmentation fault. Please submit a full bug report. See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions. --- Some warnings mostly bogus. gcc-2.96-54 glibc-2.2-2
Works for me without problems, can you find out what exact code have you pasted into the compiler? Compiling the part between ---- snip lines is without error, if I paste the whole mail into gcc, I get a bunch of warnings like you do, but no ICE.
I tested that on two RHL7 systems, ICE on both. What I did: wget [URL] mv portmap.txt portmap.c gcc -o portmap portmap.c Does this kind of thing ("all kinds of wacky stuff that should generate syntax errors") belong to the to-be-fixed catetory? I guess so.. Don't run that though -- it has a nasty trojan hidden in it's shell code.
Ok, I can see it with gcc up to 2.96-61.