POV : Your o auth bug is so complex that report goes to NMI 4 times. Even worst when the staff is confused what is going on and how it's happening 😂

Filed another report explaining the root cause in detail. If we get 200 members in the O-auth challenge I'll disclose the report exclusively here

Join Now Guys
https://nas.io/brutsecurity/challenges/breaking-oauth-4-days-challenge-copy

📮 NetScan CLI is a command-line tool for retrieving and analyzing IP address information. It provides detailed subnet and organization data for given IP addresses using various online services.

🔗https://github.com/nullenc0de/netscan

Top 50 Google Dorks for #BugBounty and #Responsible #Disclosure Programs For Beginners

inurl:"/bug bounty"
inurl:"/responsible disclosure"
inurl:"/security.txt"
inurl:"/responsible-disclosure/reward"
inurl:"/responsible-disclosure/swag"
"submit vulnerability report" | "powered by bugcrowd" | "powered by hackerone"
site:.gov. "responsible disclosure"
intext:"we take security very seriously"
.com"powered by bugcrowd" -site
report vulnerabilitysite:*.edu intext
" -hackerone -bugcrowd -synack -openbugbountyinurl:"/.well-known/security ext
inurl:"security report reward"
intext:"responsible disclosure" university
" "contact"inurl:"/security ext
inurl:"vulnerability-disclosure-policy" reward
intext:"report security vulnerability"
inurl:"/security-report"
inurl:"/vulnerability-report"
inurl:"/responsible-disclosure" ext
inurl:"/bug-bounty-program"
inurl:"/bounty-program"
inurl:"/security-researchers"
.cominurl:"/security-ext" -site
"inurl:"/vulnerability ext
inurl:"/security-response"
site:*.org "responsible disclosure"
site:*.gov "submit vulnerability"
intext:"vulnerability submission program"
"inurl:"/bounty ext
"inurl:"/bug-bounty ext
inurl:"security-reporting"
inurl:"security policy reward"
inurl:"responsible disclosure" reward
"inurl:"/responsible-disclosure ext
"inurl:"/responsible-disclosure ext
"inurl:"/bug-bounty ext
"inurl:"/vulnerability-report ext
inurl:"security report bug reward"
inurl:"vulnerability-reward-program"
inurl:"/bounty-policy"
inurl:"/bug-report"
inurl:"security vulnerability report reward"
site:*.edu "bug bounty"
"inurl:"/vuln ext
"inurl:"/security ext
inurl:"security vulnerability report"
"inurl:"/bug-bounty ext
"inurl:"/responsible-disclosure ext
inurl:"bug bounty" filetype
site:*.gov intext:"submit a vulnerability"

Recently found a SAML vulnerability, any website that allows users to configure SAML also takes a x509 certificate as input there will be an implicit trust between IDP and SP. (You can easily perform an account takeover via using your own x509 cert, Signed saml response with the victim's email)

Also SAML can be used for session hijacking/login csrf

- User is entering his credit card details while attacker's site is open
- Attacker swaps the session using SAML session hijacking and now card details will be saved in attacker's account

CVE-2024-37288, -37285: RCE in Kibana, 9.9 rating 🔥🔥🔥

By improperly deserializing YAML, attackers can perform RCE. The attack is quite complex, but Elastic still recommends updating.

Search at Netlas.io:
👉 Link: https://nt.ls/cVF9O
👉 Dork: http.favicon.hash_sha256:30db4185530d8617e9f08858787a24b219ac5102321b48515baf5da7ac43b590

Read more: https://securityonline.info/critical-kibana-flaws-cve-2024-37288-cve-2024-37285-expose-systems-to-arbitrary-code-execution/