From: Marius Muench <m.muench@vu.nl>
To: <gcc-help@gcc.gnu.org>
Cc: Fabian Freyer <mail@fabianfreyer.de>, <v.m.duta@vu.nl>,
"Cristiano Giuffrida" <c.giuffrida@vu.nl>, <pagani@cs.ucsb.edu>
Subject: Security Point of Contact
Date: Wed, 25 May 2022 18:59:54 +0200 [thread overview]
Message-ID: <1dffbaaa-04f2-9ab9-ed3a-1de20cefcff3@vu.nl> (raw)
Dear GCC maintainers,
We are a group of researchers from VU Amsterdam, UC Santa Barbara, and
independents.
We found a potential security issue with the implementation of the
Itanium C++ ABI unwinding process, and were wondering if you have any
secure email contact point we can follow up on with additional details,
or whether we should post it directly to the public bugtracker after
coordinating with other affected parties.
Either way, we would like to disclose the information as soon as possible.
Best,
Fabian, Victor, Fabio, Marius & Cristiano
next reply other threads:[~2022-05-25 17:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 16:59 Marius Muench [this message]
2022-05-25 19:35 ` Florian Weimer
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=1dffbaaa-04f2-9ab9-ed3a-1de20cefcff3@vu.nl \
--to=m.muench@vu.nl \
--cc=c.giuffrida@vu.nl \
--cc=gcc-help@gcc.gnu.org \
--cc=mail@fabianfreyer.de \
--cc=pagani@cs.ucsb.edu \
--cc=v.m.duta@vu.nl \
/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).