Difference between revisions of "Secure Coding in C and C++, Second Edition"
Jump to navigation
Jump to search
Stuffsyncbot (talk | contribs) (Automatic literature creation) |
Stuffsyncbot (talk | contribs) (Automatic literature update) |
||
| Line 1: | Line 1: | ||
{{Literature|device_name=Secure Coding in C and C++, Second Edition|image_link=https://stuff.elvis.science/uploads/accessories/accessory-image-MOcSdETjOA.jpeg|type=Book|author=Robert C. Seacord|language=English|isbn=9780321822130|publisher=2013|pages=545|references=https://www.oreilly.com/library/view/secure-coding-in/9780132981989/|description= | {{Literature|device_name=Secure Coding in C and C++, Second Edition|image_link=https://stuff.elvis.science/uploads/accessories/accessory-image-MOcSdETjOA.jpeg|type=Book|author=Robert C. Seacord|language=English|isbn=9780321822130|publisher=2013|pages=545|references=https://www.oreilly.com/library/view/secure-coding-in/9780132981989/|description= Secure Coding in C and C++, identifies and explains these root causes and shows the steps that can be taken to prevent exploitation. Moreover, this book encourages programmers to adopt security best practices and to develop a security mindset that can help protect software from tomorrow's attacks, not just today's. Drawing on the CERT's reports and conclusions, Robert C. 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 | Coverage includes technical detail on how to | ||
* Improve the overall security of any C or C++ application | |||
* Thwart buffer overflows, stack-smashing, and return-oriented programming 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 resulting from signed integer overflows, unsigned integer wrapping, and truncation errors | |||
* Perform secure I/O, avoiding file system vulnerabilities | |||
* Correctly use formatted output functions without introducing format-string vulnerabilities | |||
* Avoid race conditions and other exploitable vulnerabilities while developing concurrent code}} | |||
Latest revision as of 17:49, 1 February 2024
| Type | Book |
| Author | Robert C. Seacord |
| Language | English |
| Publisher | 2013 |
| ISBN | 9780321822130 |
| Pages | 545 |
Book Description
Secure Coding in C and C++, identifies and explains these root causes and shows the steps that can be taken to prevent exploitation. Moreover, this book encourages programmers to adopt security best practices and to develop a security mindset that can help protect software from tomorrow's attacks, not just today's. Drawing on the CERT's reports and conclusions, Robert C. 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 or C++ application
- Thwart buffer overflows, stack-smashing, and return-oriented programming 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 resulting from signed integer overflows, unsigned integer wrapping, and truncation errors
- Perform secure I/O, avoiding file system vulnerabilities
- Correctly use formatted output functions without introducing format-string vulnerabilities
- Avoid race conditions and other exploitable vulnerabilities while developing concurrent code
References
https://www.oreilly.com/library/view/secure-coding-in/9780132981989/