Never assume there’s only one way to authenticate to an API! Modern apps have many API endpoints for AuthN: /api/mobile/login | /api/v3/login | /api/magic_link; etc..
Find and test all of them for AuthN problems.
API TIP: 2/10👇🏿✔
SQL Injections used to be extremely common 5-10 years ago, and you could break almost every company?
BOLA (IDOR) is the new epidemic of API security.
As a pentester, if you understand how to exploit it, your glory is guaranteed.
Testing a Ruby on Rails App & noticed an HTTP parameter containing a URL?
Developers sometimes use "Kernel#open" function to access URLs == Game Over.
Just send a pipe as the first character and then a shell command (Command Injection by design)
API TIP: 4/10👇🏿✔
Found SSRF? use it for:
Internal port scanning
Leverage cloud services(like 169.254.169.254)
Use webhook.site
to reveal IP Address & HTTP Library
Download a very large file (Layer 7 DoS)
Reflective SSRF? disclose local mgmt consoles
API TIP: 5/31 👇🏿✔
Mass Assignment is a real thing.
Modern frameworks encourage developers to use MA without understanding the security implications.
During exploitation, don't guess object's properties names, simply find a GET endpoint that returns all of them.
API TIP: 6/10👇🏿✔
A company exposes an API for developers?
This is not the same API which is used by mobile / web application.
Always test them separately.
Don't assume they implement the same security mechanisms.
API TIP: 7/10👇🏿✔
Pentest for REST API?
Give it a chance and check if the API supports SOAP also.
Change the content-type to "application/xml", add a simple XML in the request body, and see how the API handles it.
API TIP: 8/10 👇🏿✔
Pentest for APIs?
Trying to find BOLA (IDOR) vulnerabilities?
IDs in the HTTP bodies/headers tend to be more vulnerable than IDs in URLs. Try to focus on them first.
API TIP: 9/10👇🏿✔
The API uses Authorization header?
Forget about CSRF! If the authentication mechanism doesn't support cookies, the API is protected against CSRF by design.
Thank you for Reading These these thread
All credit Goes to @traceableai
Please Follow if you like
API TIP: 10/10👇🏿✔
• • •
Missing some Tweet in this thread? You can try to
force a refresh
The Mobile Hacking CheatSheet is an attempt to summarise a few interesting basics info regarding tools and commands needed to assess the security of Android and iOS mobile applications.
While researching some neat domain based bug bounties on sites like HackerOne and BugCrowd, I've found some good vulnerable sites that pay you good money if you find something useful.
Step 1: Determine if a website is worth hacking
If the site you’re doing recon on just doesn’t look like it might be vulnerable (i.e. updated styling, utilizes PLP, looks clean),
8. Pentester Land — Written Content. 9. Checkmarx — Interactive Learning. 10. Cybrary — Written Content and Labs. 11. RangeForce — Interactive Exercises. 12. Vuln Hub — Written Content and Labs. 13. TCM Security — Interactive Learning. 14. HackXpert — Written Content and Labs.
15. Try Hack Me — Written Content and Labs. 16. OverTheWire — Written Content and Labs. 17. Hack The Box — Written Content and Labs. 18. CyberSecLabs — Written Content and Labs. 19. Pentester Academy — Written Content and Labs. 20. Bug Bounty Reports Explained YouTube — Videos.