public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "konstantin.s.serebryany at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/18043] buffer-overflow (read past the end) in wordexp/parse_dollars/parse_param
Date: Mon, 09 Mar 2015 16:42:00 -0000 [thread overview]
Message-ID: <bug-18043-131-TdS3xlqwMe@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18043-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=18043
Kostya Serebryany <konstantin.s.serebryany at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |---
--- Comment #7 from Kostya Serebryany <konstantin.s.serebryany at gmail dot com> ---
(In reply to Paul Pluzhnikov from comment #6)
> Second case fixed.
I've tweaked the fuzzer a bit and it produced something else:
pattern: "${Ca+da}"
This time reproducible only on glibc trunk so I can't reproduce with valgrind.
Can you see it?
==22916==ERROR: AddressSanitizer: heap-buffer-overflow on address
0x6020001625f2 at pc 0x7f58e333187e bp 0x7fff8223fe90 sp 0x7fff8223fe88
READ of size 1 at 0x6020001625f2 thread T0
#0 0x7f58e333187d in parse_param posix/wordexp.c:1581:18
#1 0x7f58e333187d in parse_dollars posix/wordexp.c:2103
#2 0x7f58e33212ac in parse_glob posix/wordexp.c:490:12
#3 0x7f58e33212ac in wordexp posix/wordexp.c:2416
0x6020001625f2 is located 0 bytes to the right of 2-byte region
[0x6020001625f0,0x6020001625f2)
allocated by thread T0 here:
#0 0x4a1eab in malloc
#1 0x7f58e321a546 in __add_to_environ stdlib/setenv.c:202
#2 0x7f58e332d8c3 in parse_param posix/wordexp.c:1916:4
#3 0x7f58e332d8c3 in parse_dollars posix/wordexp.c:2103
#4 0x7f58e332102b in wordexp posix/wordexp.c:2348:10
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2015-03-09 16:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 23:10 [Bug libc/18043] New: " konstantin.s.serebryany at gmail dot com
2015-02-28 3:49 ` [Bug libc/18043] " ppluzhnikov at google dot com
2015-03-06 17:14 ` cvs-commit at gcc dot gnu.org
2015-03-06 17:16 ` ppluzhnikov at google dot com
2015-03-09 4:39 ` cvs-commit at gcc dot gnu.org
2015-03-09 6:21 ` konstantin.s.serebryany at gmail dot com
2015-03-09 14:25 ` cvs-commit at gcc dot gnu.org
2015-03-09 14:28 ` ppluzhnikov at google dot com
2015-03-09 16:42 ` konstantin.s.serebryany at gmail dot com [this message]
2015-03-09 17:55 ` konstantin.s.serebryany at gmail dot com
2015-03-09 18:20 ` ppluzhnikov at google dot com
2015-03-09 18:39 ` konstantin.s.serebryany at gmail dot com
2015-03-09 18:47 ` konstantin.s.serebryany at gmail dot com
2015-03-09 18:51 ` ppluzhnikov at google dot com
2015-03-09 19:09 ` konstantin.s.serebryany at gmail dot com
2015-03-09 19:10 ` konstantin.s.serebryany at gmail dot com
2015-03-09 19:22 ` ppluzhnikov at google dot com
2015-03-09 19:28 ` konstantin.s.serebryany at gmail dot com
2015-03-09 22:25 ` ppluzhnikov at google dot com
2015-03-09 22:35 ` konstantin.s.serebryany at gmail dot com
2015-03-09 23:16 ` ppluzhnikov at google dot com
2015-03-11 15:57 ` cvs-commit at gcc dot gnu.org
2015-03-11 16:01 ` ppluzhnikov at google dot com
2015-03-19 14:55 ` fweimer at redhat dot com
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-18043-131-TdS3xlqwMe@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).