Innocent Code: A Security Wake-Up Call for Web Programmers (Paperback)

~ (Author) "The first line of the response is known as the Status-Line..." (more)
Key Phrases: metacharacter problems, data indirection, shell command injection, Cross-site Scripting, Know More, Web Trojans (more...)

Editorial Reviews

Review

the security book that all web developers need to readsound adviceignore at peril (Tech Book Report, January 2004)

"achieves its aims admirably" (PC Utilities, April 2004)

should be required reading for web developers (about.com, March 2004)

if you are a web techie you will love this book, I did (Infosecurity Today, July 04)

Product Description

This book is much more than a wake-up call. It is also an eye-opener. Even for those who are already awake to the problems of Web server security, it is a serious guide for what to do and what not to do, with many well-chosen examples. The set of fundamental rules is highly relevant.

Peter G. Neumann, Author of Computer-Related Risks,and moderator of the Internet Risks Forum (risks.org).

This concise and practical book will show where code vulnerabilities lie and how best to fix them. Its value is in showing where code may be exploited to gain access to - or break - systems, but without delving into specific architectures, programming or scripting languages or applications. It provides illustrations with real code.

Innocent Code is an entertaining read showing how to change your mindset from website construction to website destruction so as to avoid writing dangerous code. Abundant examples from susceptible sites will bring the material alive and help you to guard against:

· SQL Injection, shell command injection and other attacks based on mishandling meta-characters

· bad input

· cross-site scripting

· attackers who trick users into performing actions

· leakage of server-side secrets

· hidden enemies such as project deadlines, salesmen, messy code and tight budgets

All web programmers need to take precautions against producing websites vulnerable to malicious attack. This is the book which tells you how without trying to turn you into a security specialist.

See all Editorial Reviews

Product Details

• Paperback: 246 pages
• Publisher: Wiley; 1 edition (March 12, 2004)
• Language: English
• ISBN-10: 0470857447
• ISBN-13: 978-0470857441
• Product Dimensions: 9.1 x 7.4 x 0.6 inches
• Shipping Weight: 1 pounds (View shipping rates and policies)
• Average Customer Review: 4.6 out of 5 stars  See all reviews (5 customer reviews)
• Amazon.com Sales Rank: #1,078,768 in Books (See Bestsellers in Books)

Customer Reviews

Most Helpful Customer Reviews

18 of 18 people found the following review helpful:

5.0 out of 5 stars Focused info for developers more than security pros, March 17, 2004

By	Mike Tarrani "www.tarrani.com" (Deltona, FL USA) - See all my reviews (TOP 500 REVIEWER)    (REAL NAME)    (COMMUNITY FORUM 04)

This book is similar in many respects to Web Hacking: Attacks and Defense (ISBN 0201761769). While that book was aimed at security professionals who needed to understand the exposures and vulnerabilities in web systems that were commonly exploited by the bad guys and gals, this book is aimed more at developers.

Like for former book, this one systematically covers exposures and vulnerabilities, and provides remedies at the code level. What sets this book apart is every component of a modern web site, from web server to backend database is covered, problem areas from a developer's perspective are highlighted, and solutions for resolving the problem areas given. I like this book because developers, from casual hobbyists to professionals, will easily grasp the information. More importantly, the material is not insultingly simple to experienced developers, nor is it over the head of less experienced ones.

Another reason I like this book is in systematically uncovering exposures the QA team can also use this book as a sourcebook for developing a baseline set of test cases that will catch security-related problems during acceptance, functional qualification, or regression test cycles.

In my opinion not only should web developers (including DBAs) and QA professionals read this book, but it should also be adopted by development organizations and projects as a part of coding standards.

4 of 4 people found the following review helpful:

4.0 out of 5 stars a longer discussion of Trojans would have been nice, September 14, 2005

By	W Boudville (Terra, Sol 3) - See all my reviews (TOP 10 REVIEWER)    (REAL NAME)

Huseby walks through many instances of flawed web code. Client side and server side. All of these have been covered before in other forums and books, but he offers a clear exposition of the dangers.

Take SQL injection. If you do not have your web server filter the user's input in a web page submitted by her browser, and you blithely pass her string to your SQL engine, you are asking for grief. You're begging for a cracker to stuff a SQL command script to sabotage or exacavate your database. Thus too for shell command injection, where your server might inadvertantly execute that as a shell command. Remember to filter user input!

Cross site scripting and Trojans are also explained. Unfortunately, while the Trojan discussion is understandable, it is far too short.

There is no discussion of antiphishing methods. Though in the Trojan chapter, an example fake email would qualify as phishing. Perhaps the author saw no technical solution for phishing. And this book is about technical solutions.

6 of 7 people found the following review helpful:

5.0 out of 5 stars Highly recommended, August 6, 2004

By	Stephan Meyn "Stephan Meyn" (Sydney, Australia) - See all my reviews (REAL NAME)

Security is a serious issue and education of the developer about writing secure code is extremely important. There are a lot of books out there that write either about how to configure your servers or about the various security technologies (cryptography, WSE etc) - this is not unimportant but it is incomplete because it ignores weaknesses introduced through coding practices.
The author manages a tight and very readable book that is addressed at the software developer. It can be read in about a day or afternoon (if you happen to be stranded at an airport lounge). I will be suggesting it to be one of our standard literature titles on the development floor.