Burp Suite: by - Gurashish Arneja, Bailey Kumar
Burp Suite: by - Gurashish Arneja, Bailey Kumar
- Breach was called CVE-2017-5638, hacker could execute code by sending it into
the Content-Type Header
Web Security -SLIDE TOO SIMPLE. MAYBE ADD A
GRAPHIC
- If you build a website or web application, how do you know if it’s safe?
- Could take every precaution in the development phase and still be vulnerable
OWASP Top Ten
1. Injection
2. Broken Authentication
3. Sensitive Data Exposure
4. XML External Entities (XXE)
5. Broken Access Control
6. Security Misconfiguration
7. Cross-Site Scripting (XSS)
8. Insecure Deserialization
9. Using Components with Know Vulnerabilities
10. Insufficient Logging and Monitoring
Penetration Testing
Battering Ram - used for multiple parameters with a single payload (e.g. username
and password)
Pitchfork - a different payload for each parameter(e.g. One payload for username,
another payload for password)
Clusterbomb - a different payload for each parameter, but iterates through each
payload for each parameter. E.G. will use the password payload for username and
vice versa
Sequencer
Comparer
Spidering
request
If you guys are interested in looking at type of extensions available with BurpSuite.
I have found this great list that curates some of the most popular extensions for
Burp Suite.
https://github.com/snoopysecurity/awesome-burp-extensions#sql-injection
Decoder
- Can take input and transform it to many different formats such as base64,
hex, ascii
Allows the word “smuggled” to bypass checks be left unvalidated but executed on the
backend