This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: glibc segfault on "special" long double values is _ok_!?
- From: Jim Meyering <jim at meyering dot net>
- To: Andreas Schwab <schwab at suse dot de>
- Cc: Ulrich Drepper <drepper at redhat dot com>, bug-gnulib at gnu dot org, libc-alpha at sourceware dot org
- Date: Wed, 06 Jun 2007 15:36:53 +0200
- Subject: Re: glibc segfault on "special" long double values is _ok_!?
- References: <87y7ixb6wb.fsf@rho.meyering.net> <jeabvdmepm.fsf@sykes.suse.de>
Andreas Schwab <schwab@suse.de> wrote:
> Jim Meyering <jim@meyering.net> writes:
>
>> I'm interested, because I don't want my applications to segfault on such
>> inputs. Sure it may look a little far-fetched, but I think it's not.
>> Imagine such a bit pattern being injected into a network data stream
>> that is then printed as a long double. Just printing an arbitrary
>> "long double" should not make a server vulnerable to a DoS attack.
>
> In which way is this different from passing NULL to strlen?
I'm surprised to hear you arguing that it is desirable for glibc's printf
implementation to segfault for a long-double with an unusual bit pattern.