The Web Application Hacker's Handbook: Finding and Exploiting Security Flaws
Format: PDF / Kindle (mobi) / ePub
The highly successful security book returns with a new edition, completely updatedWeb 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.
- Reveals how to overcome the new technologies and techniques aimed at defending web applications against attacks that have appeared since the previous edition
- Discusses new remoting frameworks, HTML5, cross-domain integration techniques, UI redress, framebusting, HTTP parameter pollution, hybrid file attacks, and more
- Features a companion web site hosted by the authors that allows readers to try out the attacks described, gives answers to the questions that are posed at the end of each chapter, and provides a summarized methodology and checklist of tasks
Focusing on the areas of web application security where things have changed in recent years, this book is the most current resource on the critical topic of discovering, exploiting, and preventing web application security flaws..
which vulnerabilities (if any) were exploited, whether the attacker gained unauthorized access to data or performed any unauthorized actions, and, as far as possible, provide evidence of the intruder's identity. In any application for which security is important, key events should be logged as a matter of course. At a minimum, these typically include the following: All events relating to the authentication functionality, such as successful and failed login, and change of password Key
12, securing against cross-site scripting is an arduous task, requiring identification of each output location of user-supplied data. Although most frameworks automatically HTML-encode data when reporting errors, this is by no means universal. Error messages can appear in multiple, often unusual places within an HTTP response. In the HttpServletResponse.sendError() call used by Tomcat, the error data is also part of the response header: HTTP/1.1 500 General Error Accessing Doc10083011
physical files used to store database data, and should only be able to access this data in the intended manner using database queries with an appropriate user account. Network-level access between different infrastructure components should be filtered to permit only services with which different application tiers are intended to communicate. For example, the server hosting the main application logic may be permitted to communicate with the database server only via the port used to issue SQL
monitor the resulting requests and responses, storing all relevant details about the target application and providing numerous useful functions. The typical suite contains the following core components: An intercepting proxy A web application spider A customizable web application fuzzer A vulnerability scanner A manual request tool Functions for analyzing session cookies and other tokens Various shared functions and utilities Intercepting Proxies The
default content for any functionality or vulnerabilities that you may be able to leverage to attack the server or the application. 11.3 Test for Dangerous HTTP Methods 11.3.1. Use the OPTIONS method to list the HTTP methods that the server states are available. Note that different methods may be enabled in different directories. You can perform a vulnerability scan in Paros to perform this check. 11.3.2. Try each reported method manually to confirm whether it can in fact be used.