Skip to content
UPEEC

Secure C Coding

Avoid buffer overflows, format-string bugs, integer overflows and use-after-free.

Intermediate
Comments 0

Bound every copy, validate lengths, never pass user input as a format string (printf(s)), enable warnings (-Wall -Wextra), sanitizers and fuzzing. See SEI CERT C.

Spotted a mistake or want to add detail? Suggest an improvement — Content Contributors' edits are reviewed by editors before they go live.

Discussion (0)

Sign in or join free to ask questions and discuss this topic.