Request a Demo Contact Us

Bad API, hAPI Hackers!

 

In this presentation I’d show my methodology of looking at APIs from both black box and white box perspectives. White box meaning that I already have the Postman collection in hand so I already have all the endpoints. I’ll show how I test for technical bugs starting off by trying to leak information and error messages that discloses the framework by either changing HTTP methods, sending malformed JSON, putting it integers when it’s expecting a string, putting a string when it’s expecting an integer, etc. From there, I use what I’ve gotten and start testing for RCE, SQLi, XXE, stored XSS, etc. After the technical vulnerabilities, I’ll dig deeper into the IDORs and try to access stuff you’re not supposed to view/change, look for sensitive information leakage, etc. Sometimes it looks like there’s nothing interesting and juicy, however by combining a few endpoints together, you’re able to get something quite nice like a complete account takeover, or authentication bypass, unauthorized access, credentials and API key leaks, etc.

More resources

Datasheet

Aligning with Binding Operational Directive 20-01

Read More
Datasheet

Understanding Bug Bounty Scope

Read More
Datasheet

Trust Engineering

Read More

Get Started with Bugcrowd

Every minute that goes by, your unknown vulnerabilities leave you more exposed to cyber attacks.