Injection Vulnerabilities
Testing for Injection Vulnerabilities
SQL Injection Meta-characters
NoSQL Injection
The provided lists include SQL injection metacharacters, NoSQL injection payloads, and OS injection characters commonly used to test for vulnerabilities.
Fuzzing Wide with Postman
Injection Targets
PUT videos by id
GET videos by id
POST change-email
POST verify-email-token
POST login
GET location
POST check-otp
POST posts
POST validate-coupon
POST orders
Postman, with its Collection Runner, is used to test the entire API collection for injection vulnerabilities. The baseline is established by running the collection with well-formed requests and noting the responses. Fuzzing variables (e.g., {{fuzz}}) are added to targeted requests, and the collection is run again to observe any anomalies.
Fuzzing Deep with WFuzz
The process involves:
Duplicating the Burp Suite-captured request in a file.
Constructing a WFuzz attack command with payloads, headers, and data.
Executing WFuzz with the attack command.
Analyzing the results, filtering for successful attacks.
An example WFuzz command:
Successful injection attacks are identified by filtering responses with a status code of 200.
Troubleshooting WFuzz Attacks
For troubleshooting WFuzz attacks, it's recommended to proxy traffic to Burp Suite using the -p localhost:8080 option. This allows interception of requests in Burp Suite for detailed analysis and troubleshooting.\
This comprehensive testing approach helps identify and exploit injection vulnerabilities in the API.
Last updated
Was this helpful?
