| help | account  


Exploiting Software: How to Break Code
View Larger Image
Greg Hoglund, Gary McGraw
Addison-Wesley, Paperback, Published February 2004, 471 pages, ISBN 0201786958
List Price: $54.99
Our Price: $34.50
You Save: $20.49 (37% Off)


FREE Shipping on Orders over $40!*
Availability: Out-Of-Stock
Read an excerpt:
Chapter 3: Reverse Engineering and Program Understanding

     

Excerpt provided courtesy of Addison-Wesley Professional. Copyright © Addison-Wesley. Written permission from the publisher is required for any use of this material.

Customer Reviews: 1     Average Customer Rating:

Write a Review and tell the world about this title!

People who purchase this book frequently purchase:

Books on similar topics, in best-seller order:Books from the same publisher, in best-seller order:

How does software break? How do attackers make software break on purpose? Why are firewalls, intrusion detection systems, and antivirus software not keeping out the bad guys? What tools can be used to break software? This book provides the answers.

Exploiting Software is loaded with examples of real attacks, attack patterns, tools, and techniques used by bad guys to break software. If you want to protect your software from attack, you must first learn how real attacks are really carried out.

This must-have book may shock you--and it will certainly educate you.Getting beyond the script kiddie treatment found in many hacking books, you will learn about

  • Why software exploit will continue to be a serious problem
  • When network security mechanisms do not work
  • Attack patterns
  • Reverse engineering
  • Classic attacks against server software
  • Surprising attacks against client software
  • Techniques for crafting malicious input
  • The technical details of buffer overflows
  • Rootkits

Exploiting Software is filled with the tools, concepts, and knowledge necessary to break software.

 

Table of Contents

Foreword.

Preface.

Acknowledgments.


1. Software-the Root of the Problem.

A Brief History of Software.

The Trinity of Trouble.

The Future of Software.

Conclusion.


2. Attack Patterns.

A Taxonomy.

An Open-Systems View.

Tour of an Exploit.

Attack Patterns: Blueprints for Disaster.

An Example Exploit: Microsoft's Broken C + + Compiler.

Applying Attack Patterns.

Attack Pattern Boxes.

Conclusion.


3. Reverse Engineering and Program Understanding.

Into the House of Logic.

Should Reverse Engineering Be Illegal?

Reverse Engineering Tools and Concepts.

Approaches to Reverse Engineering.

Methods of the Reverser.

Writing IDA Plug-Ins.

Decompiling and Disassembling Software.

Decompilation in Practice: Reversing helpctr.exe.

Automatic, Bulk Auditing for Vulnerabilities.

Writing Your Own Cracking Tools.

Building a Basic Code Coverage Tool.

Conclusion.


4. Exploiting Server Software.

The Trusted Input Problem.

The Privilege Escalation Problem.

Finding Injection Points.

Input Path Tracing.

Exploiting Trust Through Configuration.

Specific Techniques and Attacks for Server Software.

Conclusion.

 

5. Exploiting Client Software.

Client-side Programs as Attack Targets.

In-Band Signals.

Cross-Site Scripting.

Clients Scripts and Malicious Code.

Content-Based Attacks.

"Back-Wash" Attacks: Leveraging Client-Side Buffering Overflows.

Conclusion.



6. Crafting (Malicious) Input.

The Defender's Dilemma.

Intrusion-Detection (not).

Partition Analysis.

Tracing Code.

Example: Reversing I-Planet Server 6.0 Through the Front Door.

Misclassification.

Building "Equivalent" Requests.

Conclusion.

Appendix: ASCII Conversion Chart.



7. Buffer Overflow.

Buffer Overflow 101.

Injection Vectors: Input Rides Again.

Buffer Overflows and Embedded Systems.

Database Buffer Overflows.

Buffer Overflows and Java?!.

Content-Based Buffer Overflow.

Audit Truncation and Filters with Buffer Overflow.

Causing Overflow and Environment Variables.

The Multiple Operation Problem.

Finding Potential Buffer Overflows.

Stack Overflow.

Arithmetic Errors in Memory Management.

Format String Vulnerabilities.

Heap Overflows.

Buffer Overflows and C + +.

Payloads.

Payloads on RISC Architectures.

Prolog/Epilog Code to Protect Functions.

Conclusion.



8. Rootkits.

Subversive Programs.

A Simple Windows-XP Kernel Rootkit.

Call Hooking.

Trojan Executable Redirection.

Hiding Files and Directories.

Patching Binary Code.

The Hardware Virus.

Low Level Disk-Access.

Adding Network Support to a Driver.

Interrupts.

Key-Logging.

Advanced Rootkit Topics.

Conclusion.


Index.

 

About the Author

Gary McGraw, Cigital's Vice President of Corporate Technology, researches software security and sets technical vision in the area of Software Risk Management. Dr. McGraw has written over sixty peer-reviewed technical publications and has functioned as principal investigator on grants from Air Force Research Labs, DARPA, National Science Foundation, and NIST's Advanced Technology Program. Dr. McGraw coauthored Java Security and Securing Java with Professor Ed Felten of Princeton, and Software Fault Injection with Jeffrey Voas.


Customer Reviews

Customer Reviews: 1     Average Customer Rating:

May 2, 2004     Kurt Oestreich (rockfuel@yahoo.com) from Kennewick, Washington
Excellent background/theoretical aspects of software security
I met Greg at Defcon 8, and his experience with finding and exploiting buffer overflows is excellent. This book gives a lot of background on why you need to be concerned about software security [but not too much space], as well as the technical aspects of compromising software security [including bypassing stack execution protection]. Greg is an excellent virtuoso at beating up windows and NT code, and while the book includes aspects of compromising windows code, it tends to be more platform independent, and provide the knowledge of how things work, rather than focusing too narrowly on a laundry list of software exploits on one itsy bitsy portion of the overall picture.

Overall, an excellent presentation. If you are interested in a more technical presentation, you may be interested in "The Shellcoder's Handbook", published by Wiley. Both books are exceptional. Greg and McGraw's "How to Break Code" is an easier read, and focuses on the understanding and theory of software security issues, while "Shellcoder's Handbook" is more focused on code and is more technical in its treatment of the subject.



Forgot your password?
FAQs
Shipping Options
Returns
Your Orders
Your Account