From: Salah Mosbah <salahbughunter@gmail.com>
To: Jeff Law <law@redhat.com>
Cc: janus@gcc.gnu.org, gcc@gcc.gnu.org, jself@gnu.org, overseers@gcc.gnu.org
Subject: Re: Security vulnerabilities affects core API authorization of gnu.org
Date: Mon, 4 Jan 2021 19:40:41 +0200 [thread overview]
Message-ID: <CAFEc1Fc4XUn7udO3024NNSxqU+VA1sXVFjxui9Y2s-0rhY1KBw@mail.gmail.com> (raw)
In-Reply-To: <ac9ccc21-c01a-a503-a598-e009e30bf4e7@redhat.com>
Hi Jeff,
Does gnu.org has a bug bounty program or reporting bugs reward policy?
On Mon, Jan 4, 2021 at 6:06 PM Jeff Law <law@redhat.com> wrote:
>
>
> On 1/4/21 3:23 AM, Salah Mosbah via Gcc wrote:
> > Hi Janus,
> >
> > How can I report some high impact security vulnerabilities that I have
> > found on gnu.org
> > web app?
> >
> > Also, does gnu.org has a bug bounty program or reporting bugs reward
> policy?
> >
> > The vulnerabilities that I have found affects the core API of gnu.org
> which
> > allows unauthorized users to get access to other user's data that they
> > don't have access to it.
> For gnu.org you'd need to contact the administrators of that domain,
> which presumably you find contact information for on www.gnu.org.
>
> If it's a problem with gcc.gnu.org, then the details should be sent to
> overseers@gcc.gnu.org
>
> Jeff
>
>
next parent reply other threads:[~2021-01-04 17:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAFEc1FcNApb65M6D6aVi=qZ6OiQ64QPGfTA558POYvS55uV=dA@mail.gmail.com>
[not found] ` <ac9ccc21-c01a-a503-a598-e009e30bf4e7@redhat.com>
2021-01-04 17:40 ` Salah Mosbah [this message]
2021-01-04 17:48 ` Jeff Law
2021-01-04 17:50 ` Frank Ch. Eigler
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=CAFEc1Fc4XUn7udO3024NNSxqU+VA1sXVFjxui9Y2s-0rhY1KBw@mail.gmail.com \
--to=salahbughunter@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=janus@gcc.gnu.org \
--cc=jself@gnu.org \
--cc=law@redhat.com \
--cc=overseers@gcc.gnu.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).