From: shhresearchers2023@gmail.com
To: mptcp@lists.linux.dev
Subject: Security Vulnerability!
Date: Sun, 04 May 2025 04:10:30 -0700 (PDT) [thread overview]
Message-ID: <68174b26.050a0220.21299b.244f@mx.google.com> (raw)
Hi Team,
I am an Independent Security Researcher running a vulnerability identification service, and I accidentally found some vulnerabilities in your infrastructure.
And it can cause damage to your website. I want to share the vulnerability details with you (includes POC, screenshots, and suggested solutions).
So tell me, may I report here? Is there any appreciation reward for a valid report/bug?
Kindly respond as soon as possible :)
LinkedIn handle: https://www.linkedin.com/in/huzaifah-s-948a26bb?utm_source=share&utm_campaign=share_via&utm_content=profile&utm_medium=ios_app
Regards,
Huzaifa Shahid
reply other threads:[~2025-05-04 11:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=68174b26.050a0220.21299b.244f@mx.google.com \
--to=shhresearchers2023@gmail.com \
--cc=mptcp@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.