Fuzzing API to identify API1: broken object level authorization control
summary
Fuzzing identifies API1 broken object-level authorization and API5 broken function-level authorization by iterating ID patterns and replacing body values derived from the OpenAPI spec, flagging endpoints that return 200 or 500 instead of 4xx. Uses open source tools like Wfuzz and OWASP ZAP, integrates generation-based fuzzing into DevSecOps (scheduled off-peak), separates QA from security testing, and experiments with machine learning to improve test-vector accuracy and raise true-positive rates.
AI-written summary · about
chapters (9)
- 0:00Intro
- 3:28Agenda
- 3:47Recent Incidents
- 5:01Access Control
- 7:28API 5 and API 1
- 11:08How can we identify
- 13:02Fuzzy factor type
- 15:19Fuzzing procedure
- 18:32Open source fuzzing tool
related talks
46mAutomating API Penetration Testing using fuzzapi
45mFuzz Testing Web APIs: Overview of Existing Tools
49mData sources for fuzzing web application APIs
35mHow to Break API's
26mOffensive API Penetration Testing
25mOWASP Top 10 for APIs
46mAPI Security – Divide & Conquer
53mFuzz Testing for Fun and Profit
