Sign In Start Free Trial

Book Overview & Buying
Table Of Contents
Feedback & Rating

Python Web Penetration Testing Cookbook

By : Cameron Buchanan, Terry Ip, Andrew Mabbitt, Benjamin May

3.5 (4)

Python Web Penetration Testing Cookbook

3.5 (4)

By: Cameron Buchanan, Terry Ip, Andrew Mabbitt, Benjamin May

Overview of this book

This book is for testers looking for quick access to powerful, modern tools and customizable scripts to kick-start the creation of their own Python web penetration testing toolbox.

Preface

Preface

What this book covers

What you need for this book

Who this book is for

Sections

Conventions

Reader feedback

Customer support

Free Chapter

1. Gathering Open Source Intelligence

1. Gathering Open Source Intelligence

Introduction

Gathering information using the Shodan API

Scripting a Google+ API search

Downloading profile pictures using the Google+ API

Harvesting additional results from the Google+ API using pagination

Getting screenshots of websites with QtWebKit

Screenshots based on a port list

Spidering websites

2. Enumeration

2. Enumeration

Introduction

Performing a ping sweep with Scapy

Scanning with Scapy

Checking username validity

Brute forcing usernames

Enumerating files

Brute forcing passwords

Generating e-mail addresses from names

Finding e-mail addresses from web pages

Finding comments in source code

3. Vulnerability Identification

3. Vulnerability Identification

Introduction

Automated URL-based Directory Traversal

Automated URL-based Cross-site scripting

Automated parameter-based Cross-site scripting

Automated fuzzing

jQuery checking

Header-based Cross-site scripting

Shellshock checking

4. SQL Injection

4. SQL Injection

Introduction

Checking jitter

Identifying URL-based SQLi

Exploiting Boolean SQLi

Exploiting Blind SQL Injection

Encoding payloads

5. Web Header Manipulation

5. Web Header Manipulation

Introduction

Testing HTTP methods

Fingerprinting servers through HTTP headers

Testing for insecure headers

Brute forcing login through the Authorization header

Testing for clickjacking vulnerabilities

Identifying alternative sites by spoofing user agents

Testing for insecure cookie flags

Session fixation through a cookie injection

6. Image Analysis and Manipulation

6. Image Analysis and Manipulation

Introduction

Hiding a message using LSB steganography

Extracting messages hidden in LSB

Hiding text in images

Extracting text from images

Enabling command and control using steganography

7. Encryption and Encoding

7. Encryption and Encoding

Introduction

Generating an MD5 hash

Generating an SHA 1/128/256 hash

Implementing SHA and MD5 hashes together

Implementing SHA in a real-world scenario

Generating a Bcrypt hash

Cracking an MD5 hash

Encoding with Base64

Encoding with ROT13

Cracking a substitution cipher

Cracking the Atbash cipher

Attacking one-time pad reuse

Predicting a linear congruential generator

Identifying hashes

8. Payloads and Shells

8. Payloads and Shells

Introduction

Extracting data through HTTP requests

Creating an HTTP C2

Creating an FTP C2

Creating an Twitter C2

Creating a simple Netcat shell

9. Reporting

9. Reporting

Introduction

Converting Nmap XML to CSV

Extracting links from a URL to Maltego

Extracting e-mails to Maltego

Parsing Sslscan into CSV

Generating graphs using plot.ly

Index

Index

Customer Reviews

3.5 (4)

5 star

50%

4 star

0%

3 star

0%

2 star

50%

1 star

0%

Testing HTTP methods

A good place to start with testing web servers is at the beginning of the HTTP request, by enumerating the HTTP methods. The HTTP method is sent by the client and indicates to the web server the type of action that the client is expecting.

As specified in RFC 7231, all web servers must support GET and HEAD methods, and all other methods are optional. As there are a lot of common methods beyond the initial GET and HEAD methods, this makes it a good place to focus testing on, as each server will be written to handle requests and send responses in a different way.

An interesting HTTP method to look out for is TRACE, as its availability leads to Cross Site Tracing (XST). TRACE is a loop-back test and basically echoes the request it receives back to the user. This means it can be used for Cross-site scripting attacks (called in this case Cross Site Tracing). To do this, the attacker gets a victim to send a TRACE request, with a JavaScript payload in the body, which would...

Visually different images

CONTINUE READING

83

Tech Concepts

36

Programming languages

73

Tech Tools

Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.

Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.

50+ new titles added per month and exclusive early access to books as they are being written.

Python Web Penetration Testing Cookbook

Search

Your notes and bookmarks