Buffer Overflow Attacks: Detect, Exploit, Prevent [Download: PDF] [Digital]

Jason Deckard (Author)

Product Details

Do you have the free reader for this item?

• Format: Adobe Reader (PDF)
• Printable: Yes. This title is printable
• Mac OS Compatible: OS 9.x or later
• Windows Compatible: Yes
• Handheld Compatible: Yes. Adobe Reader is available for PalmOS, Pocket PC, and Symbian OS.
• Digital: 304 pages
• Publisher: Syngress (February 21, 2005)
• Average Customer Review: 3.1 out of 5 stars  See all reviews (7 customer reviews)
• Amazon Best Sellers Rank: #3,913,176 Paid in Books (See Top 100 Paid in Books)
  • #26 in Books > e-Docs > By Publisher > Syngress
  • #37 in Books > e-Docs > Subjects > Computers & Internet > Security
• Required Free Software: Adobe Reader

Customer Reviews

Most Helpful Customer Reviews

16 of 19 people found the following review helpful:

4.0 out of 5 stars practical advice, February 6, 2005

By 

W Boudville (Terra, Sol 3) - See all my reviews
(VINE VOICE)    (TOP 1000 REVIEWER)    (HALL OF FAME REVIEWER)    (REAL NAME)   

This review is from: Buffer Overflow Attacks: Detect, Exploit, Prevent (Paperback)

Typically, a text on computing might give a cursory few pages (if even that!) on explaining what buffer overflow attacks are. This book takes a far more detailed look. It emphasises the writing of assembler. Which may put you, the interested reader, in a minority amongst programmers. Most of whom never write assembler.

The book teaches the writing and testing of shellcode. Very hands on. You learn to go back and forth between C source and its assembler equivalent, and how to use these when trying to induce stack overflows or attacking format strings, for example. Gritty and practical exposure. Analogous to working on a car engine. You have to get your hands dirty.

Most of the book's examples cover the Intel assembly language and the Microsoft operating systems. The book explains that this is certainly not because these are inherently riskier than alternatives. But a pragmatic reflection of Microsoft's and Intel's market dominance, which attracts attackers. For balance, examples are also shown of attacks against linux and HPUX.

9 of 10 people found the following review helpful:

2.0 out of 5 stars Proofread? Editorial and Technical reveiw?...., March 3, 2006

By 

Hadi Nahari (Mountain View, CA USA) - See all my reviews

This review is from: Buffer Overflow Attacks: Detect, Exploit, Prevent (Paperback)

For a book dedicated to such an important topic, my experience with this book was at best disappointing. This goes both for the authors (as they are primarily responsible for the material), as well as the publisher (Syngress). One would doubt whether the book has gone through any meaningful editorial review process. The errata posted on Syngress' site (bad site-design with a great deal of broken URLs in the book's relevant-links page by the way, and one "has to" sign up to obtain the errata) are utterly incomplete. The book at the time of this writing lacks an accompanying website (no reference in the errata or in the book itself).

This is an unfortunate development that one certainly notices in the recent publications pertaining to security topic, perhaps as a result of the urge to push content out to satisfy the hot-market demands.

On the technical front, the choice for the topics seems to be reasonably covering most corners; however, throughout the book there's a focus on pre-SP2 release of Microsoft Windows XP; why? If one of the objectives of the authors was to educate the audience on the topics (by providing practical and working examples), wouldn't such choice defeat the purpose?

3 of 3 people found the following review helpful:

1.0 out of 5 stars Full of errors and inconsistencies, July 29, 2008

By 

Byron Sonne (Canada) - See all my reviews
(REAL NAME)   

This review is from: Buffer Overflow Attacks: Detect, Exploit, Prevent (Paperback)

Does Syngress (the publisher) employ proof readers?

I doubt it. This book is so full of errors and inaccuracies that it becomes painful to read after a while. Especially the annotated examples, where the line numbers for the code listings often bear no relation to the line numbers listed in the accompanying analysis.

And then there's the confusion of ESP and EIP in several places throughout the book. For a collection of 'expert information' it comes off as a rather amateurish production. Makes you wonder... what else have they got wrong?

You'll notice this is very much the same as the review I've posted for "Sockets, Shellcode, Porting & Coding"... that is because it too is horrendous for errors.

This is 2 books from Syngress I've got that are very poor quality. What's going on guys?