
Download the free Kindle app and start reading Kindle books instantly on your smartphone, tablet or computer—no Kindle device required.
Read instantly on your browser with Kindle for Web.
Using your mobile phone camera, scan the code below and download the Kindle app.
Follow the authors
OK
How to Break Web Software: Functional and Security Testing of Web Applications and Web Services Paperback – 16 February 2006
Purchase options and add-ons
Rigorously test and improve the security of all your Web software!
It’s as certain as death and taxes: hackers will mercilessly attack your Web sites, applications, and services. If you’re vulnerable, you’d better discover these attacks yourself, before the black hats do. Now, there’s a definitive, hands-on guide to security-testing any Web-based software: How to Break Web Software.
In this book, two renowned experts address every category of Web software exploit: attacks on clients, servers, state, user inputs, and more. You’ll master powerful attack tools and techniques as you uncover dozens of crucial, widely exploited flaws in Web architecture and coding. The authors reveal where to look for potential threats and attack vectors, how to rigorously test for each of them, and how to mitigate the problems you find. Coverage includes
· Client vulnerabilities, including attacks on client-side validation
· State-based attacks: hidden fields, CGI parameters, cookie poisoning, URL jumping, and session hijacking
· Attacks on user-supplied inputs: cross-site scripting, SQL injection, and directory traversal
· Language- and technology-based attacks: buffer overflows, canonicalization, and NULL string attacks
· Server attacks: SQL Injection with stored procedures, command injection, and server fingerprinting
· Cryptography, privacy, and attacks on Web services
Your Web software is mission-critical–it can’t be compromised. Whether you’re a developer, tester, QA specialist, or IT manager, this book will help you protect that software–systematically.
- Print length240 pages
- LanguageEnglish
- PublisherAddison-Wesley
- Publication date16 February 2006
- Dimensions17.53 x 1.78 x 23.11 cm
- ISBN-109780321369444
- ISBN-13978-0321369444
Frequently bought together

Customers who viewed this item also viewed
Product description
From the Back Cover
"The techniques in this book are not an option for testers–they are mandatory and these are the guys to tell you how to apply them!"
–HarryRobinson, Google.
Rigorously test and improve the security of all your Web software!
It’s as certain as death and taxes: hackers will mercilessly attack your Web sites, applications, and services. If you’re vulnerable, you’d better discover these attacks yourself, before the black hats do. Now, there’s a definitive, hands-on guide to security-testing any Web-based software: How to Break Web Software.
In this book, two renowned experts address every category of Web software exploit: attacks on clients, servers, state, user inputs, and more. You’ll master powerful attack tools and techniques as you uncover dozens of crucial, widely exploited flaws in Web architecture and coding. The authors reveal where to look for potential threats and attack vectors, how to rigorously test for each of them, and how to mitigate the problems you find. Coverage includes
· Client vulnerabilities, including attacks on client-side validation
· State-based attacks: hidden fields, CGI parameters, cookie poisoning, URL jumping, and session hijacking
· Attacks on user-supplied inputs: cross-site scripting, SQL injection, and directory traversal
· Language- and technology-based attacks: buffer overflows, canonicalization, and NULL string attacks
· Server attacks: SQL Injection with stored procedures, command injection, and server fingerprinting
· Cryptography, privacy, and attacks on Web services
Your Web software is mission-critical–it can’t be compromised. Whether you’re a developer, tester, QA specialist, or IT manager, this book will help you protect that software–systematically.
Companion CD contains full source code for one testing tool you can modify and extend, free Web security testing tools, and complete code from a flawed Web site designed to give you hands-on practice in identifying security holes.
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.
Product details
- ASIN : 0321369440
- Publisher : Addison-Wesley; 1st edition (16 February 2006)
- Language : English
- Paperback : 240 pages
- ISBN-10 : 9780321369444
- ISBN-13 : 978-0321369444
- Dimensions : 17.53 x 1.78 x 23.11 cm
- Customer Reviews:
About the authors
James Whittaker is a speaker, author, futurist and distinguished engineer who specializes in creativity and stagecraft.
Discover more of the author’s books, see similar authors, read author blogs, and more
Customer reviews
Top reviews from other countries

Es werden praxisnahe nützliche Sachen besprochen. Kein großes bla bla bla über 400 Seiten, sondern wirklich up-to- the-point.

The fun starts with chapter 2 and these folks do not spend a lot of time on reconnaisance. They know how to break web software and we start on that by chapter 3. I was a little sad in chapter 5, they did not really do SQL injection justice, but then they hit it again with stored procedures in chapter 7.
If there is a weakness to the book it might be chapter 9 and 10, the ending, but I still found both chapters informative.
Every large organization I know is building web applications and most of them are doing it badly. If you are a coder, a webmaster, or a manager of any of the above, buy a copy of this book for everyone on your team. I am going to do the same for my team right now.


From the limited amount of the book I have looked at I've noticed the odd sentence which seems to me to be imperfectly crafted and the odd typo which would require a human reader to pick up. I recall "polices" instead of "policies".
My main negative impression so far just relates to the combination of the design of the book, possibly the limitations of screen capture software, and the limitations of black and white printing at the resolution used.
I think it's fair to criticise at least one design choice. There are a small number of text boxes with backgrounds which make the text hard to read (e.g. on p7, pp39-40, pp50-51 ...). The background was totally within the control of the designer and would have been better left as plain white, instead of stippled grey-shaded.
There are examples of screen dumps in the book which are hard or impossible to read (e.g on p24, p126 ...) but I can accept that the screens of some applications or websites may be hard, or impossible, to capture and print legibly in a book printed in black and white with this page size and also accept that being able to read the screen dumps is probably unnecessary to understand the surrounding text.
I don't want to give the impression that the book is overloaded with screen dumps compared with text. It is not and I think the balance is about right. I give credit to the printers for at least rendering white text on black screens quite legibly, although a magnifying glass helps.
I trust the book's many positive reviews and trust that the textual content will be helpful to me.

I am interested in the subject and glancing through things, it looks like this is exactly what I need for my work.