Book Image

The Web Application Hacker's Handbook

By : Dafydd Stuttard, Marcus Pinto
Book Image

The Web Application Hacker's Handbook

By: Dafydd Stuttard, Marcus Pinto

Overview of this book

Web applications are the front door to most organizations, exposing them to attacks that may disclose personal information, execute fraudulent transactions, or compromise ordinary users. This practical book has been completely updated and revised to discuss the latest step-by-step techniques for attacking and defending the range of ever-evolving web applications. Youíll explore the various new technologies employed in web applications that have appeared since the first edition and review the new attack techniques that have been developed, particularly in relation to the client side. The book starts with the current state of web application security and the trends that indicate how it is likely to evolve soon. Youíll examine the core security problem affecting web applications and the defence mechanisms that applications implement to address this problem, and youíll also explore the key technologies used in todayís web application. Next, youíll carry out tasks for breaking into web applications and for executing a comprehensive attack. As you progress, youíll learn to find vulnerabilities in an application's source code and review the tools that can help when you hack web applications. Youíll also study a detailed methodology for performing a comprehensive and deep attack against a specific target. By the end of this book, youíll be able to discover security flaws in web applications and how to deal with them.
Table of Contents (32 chapters)
Free Chapter
About the Authors
About the Technical Editor
MDSec: The Authors’ Company
End User License Agreement


Answers can be found at

  1. You log in to an application, and the server sets the following cookie:
    Set-cookie: sessid=amltMjM6MTI0MToxMTk0ODcwODYz;

    An hour later, you log in again and receive the following:

    Set-cookie: sessid=amltMjM6MTI0MToxMTk0ODc1MTMy;

    What can you deduce about these cookies?

  2. An application employs six-character alphanumeric session tokens and five-character alphanumeric passwords. Both are randomly generated according to an unpredictable algorithm. Which of these is likely to be the more worthwhile target for a brute-force guessing attack? List all the different factors that may be relevant to your decision.
  3. You log in to an application at the following URL:

    and the server sets the following cookie:

    Set-cookie: sessionId=1498172056438227;; path=/login; HttpOnly;

    You then visit a range of other URLs. To which of the following will your browser submit the sessionId...