Secure Coding in C and C++ (SEI Series in Software Engineering) (英語) ペーパーバック – 2005/9/9
Kindle 端末は必要ありません。無料 Kindle アプリのいずれかをダウンロードすると、スマートフォン、タブレットPCで Kindle 本をお読みいただけます。
"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
- Improve the overall security of any C/C++ application
- Thwart buffer overflows and stack-smashing attacks that exploit insecure string manipulation logic
- Avoid vulnerabilities and security flaws resulting from the incorrect use of dynamic memory management functions
- Eliminate integer-related problems: integer overflows, sign errors, and truncation errors
- Correctly use formatted output functions without introducing format-string vulnerabilities
- Avoid I/O vulnerabilities, including race conditions
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.
Robert Seacord began programming (professionally) for IBM in 1982 and has been programming in C since 1985, and in C++ since 1992. Robert is currently a Senior Vulnerability Analyst with the CERT/Coordination Center at the Software Engineering Institute (SEI). He is coauthor of Building Systems from Commercial Components (Addison-Wesley, 2002) and Modernizing Legacy Systems (Addison-Wesley, 2003). The CERT/CC, among other security-related activities, regularly analyzes software vulnerability reports and assesses the risk to the Internet and other critical infrastructure.
First: Many sections of the book are of necessity really, really boring. The chapter on integer security must set the record for most boring chapter ever written in a programming textbook. Fortunately, most of the boring parts can be skimmed over. For example, once you grok the basic idea of how an attacker can exploit a buffer overflow to overwrite the return address on the stack, you do not need to read the long discussion that shows in gory detail exactly how it is done.
Second: Although the authors are clearly very knowledgeable in their area, the book contains an occasional strangely worded phrase (and in one case a piece of code that does not do what they state it does) that leads me to suspect that the authors perhaps might not have *written* lots of code themselves.
Third: The discussion on the various tools and libraries that are available to mitigate security risks are useful, but strangely irrelevant. I have programmed on a lot of different projects in my life with a lot of different people, and I have met few, if any, people who actually use any of these tools and libraries. Further, the time that would be spent using the tools would in many cases be better spent by simply re-reading your code multiple times to find and remove the awful code that the tools are defending against and that no decent programmer should write in the first place.
That being said, the book is well written and essential reading for C and C++ programmers.
- this isn't the latest edition, so don't buy this one
- very easy to read