public inbox for glibc-bugs-regex@sourceware.org
help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs-regex@sourceware.org
Subject: [Bug regex/18014] Additional CVE assignment for regcomp denial of service (CVE-2010-4052)
Date: Tue, 24 Feb 2015 12:44:00 -0000 [thread overview]
Message-ID: <bug-18014-132-2VWzgPfd4H@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18014-132@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=18014
Florian Weimer <fweimer at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |DUPLICATE
Flags| |security-
--- Comment #1 from Florian Weimer <fweimer at redhat dot com> ---
Per our Security Exceptions, this is not a security bug:
https://sourceware.org/glibc/wiki/Security%20Exceptions
In addition, the separate between the two CVEs is unclear, so closing as a
duplicate.
*** This bug has been marked as a duplicate of bug 18013 ***
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2015-02-24 12:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 12:43 [Bug regex/18014] New: " fweimer at redhat dot com
2015-02-24 12:44 ` fweimer at redhat dot com [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-18014-132-2VWzgPfd4H@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).