bug-coreutils@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Some Dickhead <wheneveriseefeetibeatmymeat@gmail.com>,
	66835@debbugs.gnu.org
Subject: bug#66835: Heap buffer overread in expr in regexec.c in the check_arrival_add_next_nodes function.
Date: Tue, 7 Nov 2023 16:37:34 -0800	[thread overview]
Message-ID: <0bb7e4ad-2cb7-4781-a76c-6b65d994f091@cs.ucla.edu> (raw)
In-Reply-To: <CAM1cnYepiqCqwvZ_S2hN8Jj7rtfQ3LV0EisnHypqjYN_j=J14Q@mail.gmail.com>

Thanks. This is a bug in the glibc regular expression matcher. It's part 
of a well known series of bugs. See, for example:

https://sourceware.org/bugzilla/show_bug.cgi?id=12896
https://sourceware.org/bugzilla/show_bug.cgi?id=17356

It's not of much practical concern since the attacker should not have 
control of B in invocations like 'expr "$A" : "$B"'.




      reply	other threads:[~2023-11-08  0:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-29 18:14 bug#66835: Heap buffer overread in expr in regexec.c in the check_arrival_add_next_nodes function Some Dickhead
2023-11-08  0:37 ` Paul Eggert [this message]

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

  List information: https://lists.gnu.org/mailman/listinfo/bug-coreutils

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0bb7e4ad-2cb7-4781-a76c-6b65d994f091@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=66835@debbugs.gnu.org \
    --cc=wheneveriseefeetibeatmymeat@gmail.com \
    /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).