Secure Coding in C and C++¶
Seacord, R. C. (2013). Secure Coding in C and C++. Addison-Wesley.
Cited by¶
2 citations across 2 artifacts.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Escape and Leakage
- Software systems: Memory leaks where allocated resources are never deallocated; API tokens and credentials escaping into version control systems; debug information leaking into production logs and error messages; temporary files persisting beyond their intended lifecycle—failure modes Seacord (2013) catalogs in his canonical reference on secure coding in C and C++.
This sourceCanonical CERT/CC reference on software security defects; its coverage of dynamic memory management (memory leaks), resource lifecycle, and information-disclosure flaws catalogs concrete escape pathways arising from ordinary software boundary geometry.
- Software systems: Memory leaks where allocated resources are never deallocated; API tokens and credentials escaping into version control systems; debug information leaking into production logs and error messages; temporary files persisting beyond their intended lifecycle—failure modes Seacord (2013) catalogs in his canonical reference on secure coding in C and C++.
- Silent Representation Overflow
- Fixed-width arithmetic. An integer increments past its maximum and wraps; truncation of a wide value into a narrow field, two-digit year rollovers, and signed-32-bit time rollovers are the canonical cases.
This sourceStandard reference (Chapter 5, integral security) on signed integer overflow, unsigned wraparound, and truncation as silent representation failures and their mitigations (range checks, wider types).
- Fixed-width arithmetic. An integer increments past its maximum and wraps; truncation of a wide value into a narrow field, two-digit year rollovers, and signed-32-bit time rollovers are the canonical cases.
Verification¶
This reference passed the adversarial substantiation pipeline: it was checked to exist and to support the claim it is attached to. See how references were verified.
Links previously used in the corpus¶
Before the registry existed this work was also linked 1 other way.
Registry ID ref:ab1a938530fa · see in the full table