November 2017
Intermediate to advanced
452 pages
11h 46m
English
While using lower level languages such as C, there is a high chance of memory corruption bugs arising if bounds are not properly checked and validated by developers programmatically. Preventing the use of known dangerous functions and APIs aids against memory-corruption vulnerabilities within firmware. For example, a non-exhaustive list of known, unsafe C functions consists of: strcat, strcpy, sprintf, scanf, and gets. Common memory-corruption vulnerabilities such as buffer overflows or heap overflows can consist of overflowing the stack or the heap. The impact of these specific memory-corruption vulnerabilities when exploited differ per the operating system platform. For example, commercial RTOS ...
Read now
Unlock full access