https://www.bugbountyhunter.com/zseano/
زیشانو متودولوژی
بهترین واسه مایندست و کسایی که میخوان بدون ریکان باگ بزنن.
یکم قدیمیه ولی خیلی کامله
زیشانو متودولوژی
بهترین واسه مایندست و کسایی که میخوان بدون ریکان باگ بزنن.
یکم قدیمیه ولی خیلی کامله
❤1
https://www.youtube.com/watch?v=s6cwbmtyFCE&t=1525s
The Art of Recon: Strategies for Modern Asset Discovery
By Shubs
The Art of Recon: Strategies for Modern Asset Discovery
By Shubs
🔥2👍1
https://joaxcar.com/blog/2024/02/19/csp-bypass-on-portswigger-net-using-google-noscript-resources/
CSP bypass
CSP bypass
Johan Carlsson
CSP bypass on PortSwigger.net using Google noscript resources - Johan Carlsson
Portswigger just disclosed a report of mine over on HackerOne. It’s an unusual report in that the issue reported is purely a CSP bypass. I thought that I could provide a bit of context to the report to answer some questions raised in relation to it. First…
🔥2
During a recent CTF, one participant found a particularly interesting solution to my challenge. The goal was to send multiple CSRF requests with SameSite=Lax from 1 visit.
Normally, a form sends you to the page you are posting to and you cannot send any more CSRF requests.
My intended solution was to use
The unintended technique was something I hadn't seen before. Regular CSRFs often use <form>'s for top-level navigations, but it seems like we cannot control the browser anymore after submitting the form.
But, by cancelling the navigation, it is possible to regain control.
After the request is sent, while waiting for a response from the target, call
https://gist.github.com/JorianWoltjer/b9163fe616319db8fe570b4ef9c02291
reference:
https://x.com/J0R1AN/status/1842139861295169836
#csrf #twitter
Normally, a form sends you to the page you are posting to and you cannot send any more CSRF requests.
My intended solution was to use
<link rel="prerender" href="..."> to send an authenticated GET request to the CSRF-able endpoint, repeatable without leaving the attacker's page. Prerender represents the full navigation as closely as possible, sending SameSite=Lax cookies. The unintended technique was something I hadn't seen before. Regular CSRFs often use <form>'s for top-level navigations, but it seems like we cannot control the browser anymore after submitting the form.
But, by cancelling the navigation, it is possible to regain control.
After the request is sent, while waiting for a response from the target, call
window.stop() or submit another form to cancel the previous form. Timing can be measured and is surprisingly consistent. Check out the PoC's here:https://gist.github.com/JorianWoltjer/b9163fe616319db8fe570b4ef9c02291
reference:
https://x.com/J0R1AN/status/1842139861295169836
#csrf #twitter
❤1
Attacking Secondary Contexts in Web Applications.pdf
2.7 MB
Attacking Secondary Contexts in Web Applications
خیلی عالیههه🔥
خیلی عالیههه🔥
👌5👍2
guys have a look this contains all waf bypass payloads people posted that worked for them this will help you better in wafbypass on bbp..
https://github.com/waf-bypass-maker/waf-community-bypasses/blob/main/payloads.twitter.csv
https://github.com/waf-bypass-maker/waf-community-bypasses/blob/main/payloads.twitter.csv
GitHub
waf-community-bypasses/payloads.twitter.csv at main · waf-bypass-maker/waf-community-bypasses
Contribute to waf-bypass-maker/waf-community-bypasses development by creating an account on GitHub.
❤7