Adobe® Digital Editions software.This eBook requires the free
Before downloading this DRM-encrypted PDF, be sure to:
A code companion developers will turn to again and again as they seek to protect their systems from attackers.
° Important book because so many programs continue to be written in C/C++ -- languages that do not include any built-in security safeguards for programmers and the resulting code.
° Contains hundreds of examples of secure and insecure code as well as sample exploits.
° This book taps into invaluable CERT work in identifying, analyzing, and overcoming software vulnerabilities.
"The security of information systems has not improved at a rate consistent with the growth and sophistication of the attacks being made against them. To address this problem, we must improve the underlying strategies and techniques used to create our systems. Specifically, we must build security in from the start, rather than append it as an afterthought. That's the point of Secure Coding in C and C++. In careful detail, this book shows software developers how to build high-quality systems that are less vulnerable to costly and even catastrophic attack. It's a book that every developer should read before the start of any serious project."
--Frank Abagnale, author, lecturer, and leading consultant on fraud prevention and secure documents
Commonly exploited software vulnerabilities are usually caused by avoidable software defects. Having analyzed nearly 18,000 vulnerability reports over the past ten years, the CERT/Coordination Center (CERT/CC) has determined that a relatively small number of root causes account for most of them. This book identifies and explains these causes and shows the steps that can be taken to prevent exploitation. Moreover, this book encourages programmers to adopt security best practices and develop a security mindset that can help protect software from tomorrow's attacks, not just today's.
Drawing on the CERT/CC's reports and conclusions, Robert Seacord systematically identifies the program errors most likely to lead to security breaches, shows how they can be exploited, reviews the potential consequences, and presents secure alternatives.
Coverage includes technical detail on how to
Secure Coding in C and C++ presents hundreds of examples of secure code, insecure code, and exploits, implemented for Windows and Linux. If you're responsible for creating secure C or C++ software--or for keeping it safe--no other book offers you this much detailed, expert assistance.
Download the Sample
Chapter related to this title.
About the Author.
1. Running with Scissors.
Gauging the Threat
C and C++
Common String Manipulation Errors
Process Memory Organization
3. Pointer Subterfuge.
Modifying the Instruction Pointer
Global Offset Table
The .dtors Section
The atexit() and on_exit() Functions
The longjmp() Function
4. Dynamic Memory Management.
Dynamic Memory Management
Common Dynamic Memory Management Errors
Doug Lea's Memory Allocator
5. Integer Security.
Integer Error Conditions
Nonexceptional Integer Logic Errors
6. Formatted Output.
Formatted Output Functions
Exploiting Formatted Output Functions
7. File I/O.
Time of Check, Time of Use
Files as Locks and File Locking
File System Exploits
8. Recommended Practices.
Secure Software Development Principles
Systems Quality Requirements Engineering
Architecture and Design
Defense in Depth
The CERT Coordination Center (CERT/CC) was formed by the Defense Advanced Research Projects Agency (DARPA) in November 1988 in response to the Morris worm incident, which brought ten percent of Internet systems to a halt in November 1988. The CERT/CC is located in Pittsburgh, Pennsylvania, at the Software Engineering Institute (SEI), a federally funded research and development center sponsored by the U.S. Department of Defense.
The initial focus of the CERT/CC was incident response and analysis. Incidents include successful attacks such as compromises and denial of service, as well as attack attempts, probes, and scans. Since 1988, the CERT/CC has received more than 22,665 hotline calls reporting computer security incidents or requesting information, and has handled more than 319,992 computer security incidents. The number of incidents reported each year continues to grow.
Responding to incidents, while necessary, is insufficient to secure the Internet and interconnected information systems. Analysis indicates that the majority of incidents are caused by trojans, social engineering, and the exploitation of software vulnerabilities, including software defects, design decisions, configuration decisions, and unexpected interactions between systems. The CERT/CC monitors public sources of vulnerability information and regularly receives reports of vulnerabilities. Since 1995, more than 16,726 vulnerabilities have been reported. When a report is received, the CERT/CC analyzes the potential vulnerability and works with technology producers to inform them of security deficiencies in their products and to facilitate and track their response to those problems.
Similar to incident reports, vulnerability reports continue to grow at an alarming rate. While managing vulnerabilities pushes the process upstream, it is again insufficient to address the issues of Internet and information system security. To address the growing number of both vulnerabilities and incidents, it is increasingly apparent that the problem must be attacked at the source by working to prevent the introduction of software vulnerabilities during software development and ongoing maintenance. Analysis of existing vulnerabilities indicates that a relatively small number of root causes account for the majority of vulnerabilities. The goal of this book is to educate developers about these root causes and the steps that can be taken so that vulnerabilities are not introduced.
Secure Coding in C and C++ should be useful to anyone involved in the development or maintenance of software in C and C++.
Secure Coding in C and C++ provides practical advice on secure practices in C and C++ programming. Producing secure programs requires secure designs. However, even the best designs can lead to insecure programs if developers are unaware of the many security pitfalls inherent in C and C++ programming. This book provides a detailed explanation of common programming errors in C and C++ and describes how these errors can lead to code that is vulnerable to exploitation. The book concentrates on security issues intrinsic to the C and C++ programming languages and associated libraries. It does not emphasize security issues involving interactions with external systems such as databases and web servers, as these are rich topics on their own. The intent is that this book be useful to anyone involved in developing secure C and C++ programs regardless of the specific application.
Secure Coding in C and C++ is organized around functional capabilities commonly implemented by software engineers that have potential security consequences, such as formatted output and arithmetic operations. Each chapter describes insecure programming practices and common errors that can lead to vulnerabilities, how these programming flaws can be exploited, the potential consequences of exploitation, and secure alternatives. Root causes of software vulnerabilities, such as buffer overflows, integer type range errors, and invalid format strings, are identified and explained where applicable. Strategies for securely implementing functional capabilities are described in each chapter, as well as techniques for discovering vulnerabilities in existing code.
This book contains the following chapters:
Secure Coding in C and C++ contains hundreds of examples of secure and insecure code as well as sample exploits. Almost all of these examples are in C and C++, although comparisons are drawn with other languages. The examples are implemented for Windows and Linux operating systems. Unless otherwise stated, Microsoft Windows examples are compiled using Visual C++ .NET and tested on Windows 2000 Professional platform with an Intel Pentium 4 processor while Linux examples are compiled with GNU gcc/g++ and tested running Red Hat Linux 9 on an Intel Pentium 4 processor.
While the specific examples have typically been compiled and tested in one or more of these environments, vulnerabilities are evaluated to determine whether they are specific to or generalizable across compiler version, operating system, microprocessor, applicable C or C++ standards, little or big endian architectures, and execution stack architecture.
This book focuses on programming flaws in C and C++ that are the most common causes of software vulnerabilities. However, because of size and space constraints, not every potential source of vulnerabilities is covered. Vulnerabilities discussed in the book are also cross-referenced with real-world examples from the US-CERT Vulnerability Notes Database at www.kb.cert.org/vuls/.
Download the Foreword
file related to this title.
Download the Index
file related to this title.