From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Siddhesh Poyarekar via Libc-alpha <libc-alpha@sourceware.org>
Cc: Florian Weimer <fweimer@redhat.com>, Carlos O'Donell <carlos@redhat.com>
Subject: 'trusted and reasonably structured' regular expressions
Date: Wed, 24 Feb 2021 10:23:13 +0530 [thread overview]
Message-ID: <2152f614-0003-8dcf-f5cd-2d12c4e77e28@gotplt.org> (raw)
Hi,
The security exceptions[1] wiki page mentions that buffer overflows and
other similar bugs will be treated as security vulnerabilities provided
(well it actually says 'assuming' but I interpreted it as 'provided')
that the offending pattern is 'trusted and reasonably well structured'.
It appears to offload the responsibility of sanitizing regular
expressions to the caller, which seems like the responsibility of the
regular expression library. We have not rejected CVEs on this basis in
the past[2] but it seems like something we should remedy as a policy.
It seems unreasonable to me to expect users to parse regular expressions
to validate them before passing them on to the regular expression parser
library.
Thoughts?
Siddhesh
[1] https://sourceware.org/glibc/wiki/Security%20Exceptions
[2] https://sourceware.org/bugzilla/show_bug.cgi?id=24114
next reply other threads:[~2021-02-24 4:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 4:53 Siddhesh Poyarekar [this message]
2021-02-24 18:16 ` Paul Eggert
2021-02-24 19:18 ` Florian Weimer
2021-02-24 19:49 ` Paul Eggert
2021-02-24 19:56 ` Florian Weimer
2021-02-24 22:37 ` Joseph Myers
2021-02-25 2:51 ` Siddhesh Poyarekar
2021-02-25 3:03 ` Zack Weinberg
2021-02-25 3:15 ` Siddhesh Poyarekar
2021-02-25 3:26 ` Zack Weinberg
2021-02-25 4:53 ` Paul Eggert
2021-02-25 5:27 ` Siddhesh Poyarekar
2021-02-26 21:12 ` Paul Eggert
2021-03-02 10:58 ` Siddhesh Poyarekar
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=2152f614-0003-8dcf-f5cd-2d12c4e77e28@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@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).