public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/18099] a.out: wordexp.c:1937: parse_param: Assertion `value != ((void *)0)' failed.
Date: Tue, 21 Jul 2015 10:39:00 -0000 [thread overview]
Message-ID: <bug-18099-131-fTmrxCIoFR@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18099-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=18099
--- Comment #3 from Florian Weimer <fweimer at redhat dot com> ---
(In reply to Florian Weimer from comment #1)
> Reachable even with WRDE_NOCMD, so this is a security issue in builds with
> asserts enabled (which we support).
This is incorrect because wordexp is inherently DoS-prone with crafted
patterns.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2015-07-21 10:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 21:08 [Bug libc/18099] New: " konstantin.s.serebryany at gmail dot com
2015-03-19 15:08 ` [Bug libc/18099] " fweimer at redhat dot com
2015-07-12 8:08 ` neleai at seznam dot cz
2015-07-21 10:39 ` fweimer at redhat dot com [this message]
2015-08-27 22:26 ` [Bug glob/18099] " jsm28 at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-18099-131-fTmrxCIoFR@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).