Pub. Date:
Pearson Education
How to Break Web Software: Functional and Security Testing of Web Applications and Web Services / Edition 1

How to Break Web Software: Functional and Security Testing of Web Applications and Web Services / Edition 1

by Mike Andrews, James WhittakerMike Andrews
Current price is , Original price is $54.99. You

Temporarily Out of Stock Online

Please check back later for updated availability.


Learn how web testing can help prepare for and prevent attacks on web applications

Product Details

ISBN-13: 9780321369444
Publisher: Pearson Education
Publication date: 02/16/2006
Pages: 240
Product dimensions: 6.90(w) x 9.10(h) x 0.70(d)

About the Author

Mike Andrews is a senior consultant at Foundstone who specializes in software security and leads the Web application security assessments and Ultimate Web Hacking classes. He brings with him a wealth of commercial and educational experience from both sides of the Atlantic and is a widely published author and speaker. Before joining Foundstone, Mike was a freelance consultant and developer of Web-based information systems, working with clients such as The Economist, the London transport authority, and various United Kingdom universities. In 2002, after being an instructor and researcher for a number of years, Mike joined the Florida Institute of Technology as an assistant professor, where he was responsible for research projects and independent security reviews for the Office of Naval Research, Air Force Research Labs, and Microsoft Corporation. Mike holds a Ph.D. in computer science from the University of Kent at Canterbury in the United Kingdom, where his focus was on debugging tools and programmer psychology.

James A. Whittaker is a professor of computer science at the Florida Institute of Technology (Florida Tech) and is founder of Security Innovation. In 1992, he earned his Ph.D. in computer science from the University of Tennessee. His research interests are software testing, software security, software vulnerability testing, and anticyber warfare technology. James is the author of How to Break Software (Addison-Wesley, 2002) and coauthor (with Hugh Thompson) of How to Break Software Security (Addison-Wesley, 2003), and over fifty peer-reviewed papers on software development and computer security. He holds patents on various inventions in software testing and defensive security applications and has attracted millions in funding, sponsorship, and license agreements while a professor at Florida Tech. He has also served as a testing and security consultant for Microsoft, IBM, Rational, and many other United States companies.

In 2001, James was appointed to Microsoft’s Trustworthy Computing Academic Advisory Board and was named a “Top Scholar” by the editors of the Journal of Systems and Software, based on his research publications in software engineering. His research team at Florida Tech is known for its testing technologies and tools, which include the highly acclaimed runtime fault injection tool Holodeck. His research group is also well known for their development of exploits against software security, including cracking encryption, passwords and infiltrating protected networks via novel attacks against software defenses.

Table of Contents

Preface vii

Acknowledgments ix

About the Authors xi

Chapter 1: The Web Is Different 1

Chapter 2: Gathering Information on the Target 11

Chapter 3: Attacking the Client 29

Chapter 4: State-Based Attacks 41

Chapter 5: Attacking User-Supplied Input Data 65

Chapter 6: Language-Based Attacks 85

Chapter 7: Attacking the Server 99

Chapter 8: Authentication 115

Chapter 9: Privacy 135

Chapter 10: Web Services 149

Appendix A: Fifty Years of Software: Key Principles for Quality 159

Appendix B: Flowershop Bugs 171

Appendix C: Tools 179

Index 207


Preface Numerous times we've been asked when the next book in the How to Break... series will come out and what it's going to be about. The overwhelming request from our readers has been on the subject of Web applications. It seems many testers find they are working in this area and are facing the prospect of testing applications that employ applications' specialized protocols and languages that exist on the World Wide Web.

Although many of the tests from How to Break Software (Addison-Wesley, 2002) and How to Break Software Security (Addison-Wesley, 2003) are relevant in this environment, applications hosted on the Internet do suffer from some unique problems. This book tackles those problems in the same spirit of its predecessors with a decided slant toward security issues in Web applications.

Before we go into what this book is all about, first let us tell you what it isn't all about. We are not trying to rewrite the Hacking Exposed books. Although there is an overlap of subject matter with the hacking literature, our intention is not to show how to exploit a Web server or Web application. Our focus is about how to test Web applications for common failures that can lead to such exploitation.

How to Break Web Software is a book written for software developers, testers, managers, and quality assurance professionals to help put the hackers out of business.

This focus necessarily means knowledge of hacker techniques is included in this book. After all, one needs to understand the techniques of their adversary in order to counter them. But, this book is about testing, not about exploitation. Our focus is to guide testers toward areas of the application that are prone to problems and methods of rooting them out.

This book isn't about creating a correct Web application architecture, nor is it about coding Web applications. There are other published opinions on this and each Web development platform has its own unique challenges that must be considered, which books like Innocent Code do so well. How to Break Web Software, however, does contain a lot of information about how not to architect and code a Web application. Thus, Web developers would be wise to consider it as part of their reference library on secure Web programming.

What this book is about is pointing the tester toward specific attacks to try on their application to test its defenses. We will be looking at classic examples of malicious input, ways of bypassing validation and authorization checks, as well as problems inherited from certain configurations/languages/architectures—all in a simple format that will show where to look for the problem, how to test for the problem, and advice on methods of mitigation. How to Break Web Software is intended as a one-stop shop for people to dip into to get information (and inspiration) to test web-based applications for common problems.

Happy Web testing!

Mike Andrews, Orange County, California

James A. Whittaker, Melbourne, Florida

© Copyright Pearson Education. All rights reserved.

Customer Reviews