Kunal Pandey
1.4K posts

Kunal Pandey
@kunalp94
Love to poke at web, android and desktop Apps. https://t.co/Cd3jlZlNEu || Synack Red Teamer @synack
IN Katılım Ocak 2013
253 Takip Edilen4.5K Takipçiler

Truly honoured to be recognized as Titan at @synack and named Mentor of the Year. It’s a privilege to stand alongside some of the top security professionals in the industry. Thank you all :)
English

🎉 Congratulations 🎉, the winners are
@KavanSoni_07
@manish1221singh
@pratikcyb
@being__aman
@scarcemrk
@darkrider758
@iammeera_
@pandyaMayur11
@Mitin_sharma_22
@chalcidfly
Keep your DM open. I will be contacting you directly. Enjoy the conference.
Kunal Pandey@kunalp94
🎉 Giveaway Alert! 🎉 Hello everyone, I’m giving away 10 students passes for @bsidesahmedabad. Just comment below why you wanna attend the event and like the tweet. Good luck.
English

🎉 Giveaway Alert! 🎉
Hello everyone, I’m giving away 10 students passes for @bsidesahmedabad.
Just comment below why you wanna attend the event and like the tweet.
Good luck.
English

@0xMstar @krishnsec @zseano @Tur24Tur You can try encoded html entity in between
jav%26Tab%3bscript://google.com/%0dalert(1)
(	 —> %26Tab%3b)
Only if the above value is reflecting on href link.
or try %0c in between the javascript protocol.
English

Got this on one of the BB program , do you see problem here?, I reported this on bugcrowd Hackercup 2 years back & in collaboration with @krishnsec @zseano @Tur24Tur , It was in resolved state for 1 year, Recently revisited this & reported.

English

@carbonmanx @zseano The element "style" will trigger the above event handler as the content-visibility has been as auto. Using double quotes and adding "style element will trigger above XSS.
English

this works on latest version of chrome. no more user interaction needed for hidden input xss :) thanks for sharing!
Masato Kinugawa@kinugawamasato
ooh, this works on Chrome Canary :D <input type="hidden" oncontentvisibilityautostatechange="alert(/ChromeCanary/)" style="content-visibility:auto">
English

@kunalp94 Thankyou,that WireServer thing looks interesting but I have been strictly told to focus on escalating the impact via the Oauth token only 🥲(the bug is actually fixed still they reverted the changes on the dev env just so that I can have a chance escalating it with that condition
English

@Rhynorater Nice IDN homograph attack on the redirection parameter by @Yassineaboukir :)
hackerone.com/reports/861940
English

Ways to leak oauth code in app:
* Bad redir URL host (can redirect to badexample[.]com not just example[.]com)
* Bad redir URL host via . regex issue (can redirect to wwwXexample[.]com instead of www[.]example[.]com)
* Bad redir URL path (redir to a path the attacker can leak via application logic)
* Parameter injection in redir URL %3f -> ? adding parameters or breaking restriction logic
* HTML Injection + permissive redir URL path (img tag + meta tag referrer policy)
* PostMessage leak of URL
* Open redirect
Got any others?
English

Another Sharepoint Rest API documentation by Microsoft:
learn.microsoft.com/en-us/previous…
English

If you see a site with " _layout/*" endpoints or in source code, then it runs on Microsoft SharePoint.
Here is the API endpoint list that you can still test:
s-kainet.github.io/sp-rest-explor…
It's a complete list but you can still check out Microsoft sharepoint documentation.
English







