SSRF (Server Site Request Forgery)on – SQLi Basic

Hi Slack Security Team,

Here is Shaifullah Shaon (Black_EyE), An Ethical Hacker.
a white hat cyber security researcher from Bangladesh reporting a serious
[3’rd ranking in OWASP] security vulnerability on your system.

I faced a technical security bug called “SSRF (Server Site Request Forgery)on”.

Now I exploited it. If you verify more, so you can see my video poc that was unlisted my youtube channel.

Let’s follow me,

1. I already Open my Account.
2. I was create an app which I installed into my cheat box.
3. Now I use /comamnd which I was set a url
4. Now I put /comma (Slash command) on message box.
   SSRF Testing APP 10:39 AM
   Only visible to you
   SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.8
   As you see, Here showing The Open SSH Version.
5. Now I am change website url from to (This is my Own ssh) and use my 55 Port.
6. Now again put /comma (Slash command) on message box.
7. As you see here, Slack message box showing me 503 (Timeout was reached). But Here see my ssh. I was forwarded my 55 no port using netcat.
    nc -lnvvp 55
    listening on [::]:55 …
   here was port listing, Now when see the 503 (Timeout was reached) from message box, Here I get user token from your server.

User-Agent: Slackbot 1.0 (+
Accept-Encoding: gzip,deflate
Accept: application/json,*/*
Content-Length: 298
Content-Type: application/x-www-form-urlencoded
Cache-Control: max-age=259200
Connection: keep-alive

** Note: An attacker can stole user token using this issue.

Please See my Video Poc for understand clearly. Hopefully Those are Very critical issue.
Resolve those issue as soon as possible.

Here is proof as video concept (unlisted):

Thank you
Shaifullah Shaon (Black_EyE)

It’s an Online It Section
Please Subscribe us.

Leave a Reply

Your email address will not be published. Required fields are marked *

Name *
Email *