public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "helmut at subdivi dot de" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/18036] buffer overflow (read past end of buffer) in internal_fnmatch=>end_pattern with "**(!()" pattern
Date: Tue, 06 Jun 2023 12:24:46 +0000 [thread overview]
Message-ID: <bug-18036-131-brezyyZihh@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18036-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=18036
Helmut Grohne <helmut at subdivi dot de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |helmut at subdivi dot de
--- Comment #5 from Helmut Grohne <helmut at subdivi dot de> ---
While this bug has been tracked together with
https://sourceware.org/bugzilla/show_bug.cgi?id=18032 as CVE-2015-8984 e.g. in
RedHat https://bugzilla.redhat.com/show_bug.cgi?id=1197730#c3, that's not
universally the case and e.g. Debian missed this fix in Debian 8 while
including the other. As such, I think it would be best to track these
separately using separate CVE identifiers. Would you want to request one or
should I request via the standard mitre interface?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-06-06 12:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 18:12 [Bug libc/18036] New: " konstantin.s.serebryany at gmail dot com
2015-02-26 18:22 ` [Bug libc/18036] " ppluzhnikov at google dot com
2015-02-28 5:07 ` ppluzhnikov at google dot com
2015-03-02 21:37 ` cvs-commit at gcc dot gnu.org
2015-03-02 21:38 ` ppluzhnikov at google dot com
2023-06-06 12:24 ` helmut at subdivi dot de [this message]
2023-06-25 20:38 ` carnil at debian dot org
2023-06-25 20:38 ` carnil at debian dot 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-18036-131-brezyyZihh@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).