From: Jeffrey Walton <noloader@gmail.com>
To: Muhammad javad <mh.sec262@gmail.com>
Cc: bzip2-devel@sourceware.org
Subject: Re: Vulnerability in your website
Date: Mon, 7 Feb 2022 15:07:33 -0500 [thread overview]
Message-ID: <CAH8yC8=FmHvucZya+=p-k6fGZPoChfPP4CfHtZ=fU_eKFuMWwg@mail.gmail.com> (raw)
In-Reply-To: <CAKhtc+FtCyMLPdOWjmZtU8euJ3T4yoSZZtHx6Og0=dqpDQ0ksw@mail.gmail.com>
On Mon, Feb 7, 2022 at 1:10 PM Muhammad javad via Bzip2-devel
<bzip2-devel@sourceware.org> wrote:
>
> I found a vulnerability in your website and want to disclose it to you.
>
> Let me know if you have any active bug bounty program or is there any
> compensation for reporting vulnerabilities?
>
> Looking forward to hearing from you
Sourceware hosts the Bzip2 site. You should be able to reach the
Adminstrative and Technical contacts via a WHOIS lookup. But it looks
like they fail to publish the required information (this is an ICANN
contractual requirement):
$ whois sourceware.org | grep '@'
Registrar Abuse Contact Email: registrar-abuse@google.com
And I don't think registrar-abuse@google.com is who you want to contact.
I also can't find a security contact while searching the sourceware
site. Confer, https://www.sourceware.org/ and
https://www.google.com/search?q=security+contact+site:sourceware.org.
The page https://www.sourceware.org/suggestions.html offers
sourcemaster@sourceware.org. Maybe it will work (?).
Maybe try webmaster@sourceware.org, secure@sourceware.org or
security@sourceware.org? They may be conforming to RFC2142.
That's no way to run a railroad, as they say.
Jeff
next prev parent reply other threads:[~2022-02-07 20:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 18:09 Muhammad javad
2022-02-07 20:07 ` Jeffrey Walton [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-02-07 18:05 Muhammad javad
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='CAH8yC8=FmHvucZya+=p-k6fGZPoChfPP4CfHtZ=fU_eKFuMWwg@mail.gmail.com' \
--to=noloader@gmail.com \
--cc=bzip2-devel@sourceware.org \
--cc=mh.sec262@gmail.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).