public inbox for glibc-bugs-regex@sourceware.org
help / color / mirror / Atom feed
From: "eggert at cs dot ucla.edu" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs-regex@sourceware.org
Subject: [Bug regex/28470] New: Buffer read overrun in regular expression searching
Date: Mon, 18 Oct 2021 22:07:19 +0000 [thread overview]
Message-ID: <bug-28470-132@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=28470
Bug ID: 28470
Summary: Buffer read overrun in regular expression searching
Product: glibc
Version: 2.34
Status: NEW
Severity: normal
Priority: P2
Component: regex
Assignee: eggert at cs dot ucla.edu
Reporter: eggert at cs dot ucla.edu
CC: drepper.fsp at gmail dot com
Target Milestone: ---
Created attachment 13724
--> https://sourceware.org/bugzilla/attachment.cgi?id=13724&action=edit
Patch glibc read buffer overrun in re_search_internal
The glibc regular expression matcher can overrun a read buffer when ignoring
case in a multibyte locale. Patch attached. I do not have a test case; I
suppose a test case could be derived from Benno's email, cited in the patch.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-10-18 22:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-18 22:07 eggert at cs dot ucla.edu [this message]
2021-10-18 22:07 ` [Bug regex/28470] " eggert at cs dot ucla.edu
2021-10-21 13:05 ` schwab@linux-m68k.org
2021-11-24 22:31 ` eggert at cs dot ucla.edu
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-28470-132@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs-regex@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).