public inbox for glibc-bugs-regex@sourceware.org
help / color / mirror / Atom feed
From: "bonzini at gnu dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs-regex@sources.redhat.com
Subject: [Bug regex/12896] regexec() stack overflow denial of service
Date: Sat, 18 Jun 2011 13:20:00 -0000 [thread overview]
Message-ID: <bug-12896-132-tUk7SJAPC3@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12896-132@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=12896
Paolo Bonzini <bonzini at gnu dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |bonzini at gnu dot org
Resolution| |INVALID
--- Comment #1 from Paolo Bonzini <bonzini at gnu dot org> 2011-06-18 13:20:13 UTC ---
This is not really a vulnerability in glibc; in various forms, it is common to
pretty much any regular expression engine.
In general, applications should not pass to regcomp regular expressions coming
from untrusted sources. The glibc implementations ensures that "good" regular
expressions, in particular not including very high repetition counts or
backreferences, do not cause anomalous stack usage in either regcomp or
regexec. This is usually a sufficient guarantee.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2011-06-18 13:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-16 3:07 [Bug regex/12896] New: " yangdingning at gmail dot com
2011-06-18 13:20 ` bonzini at gnu dot org [this message]
2014-06-13 10:56 ` [Bug regex/12896] " fweimer at redhat dot com
2014-06-19 14:45 ` fweimer at redhat dot com
2015-02-24 11:58 ` 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-12896-132-tUk7SJAPC3@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs-regex@sources.redhat.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).