| Aspect | MISRA-C:2012 | CERT-C Coding Standard |
|---|---|---|
| Focus | Safety: predictable, deterministic behaviour | Security: prevent exploitable vulnerabilities |
| Mandatory? | Referenced by ISO 26262 | Required by ISO/SAE 21434, UNECE R155 |
| Rule count | ~160 rules + directives | ~100+ rules across categories |
| Deviations | Formal deviation process | Not applicable (must comply or risk accepting) |
| Key categories | Language subset, type safety | Integer overflow, buffer overrun, format strings, race conditions |
CERT-C: SEI CERT C Coding Standard
Integer Security Rules
#include
#include
/* CERT INT30-C: Ensure unsigned integer operations do not wrap */
/* Unsigned wrapping is defined but often a logic error */
uint32_t safe_add_u32(uint32_t a, uint32_t b, uint32_t *result)
{
if (b > (UINT32_MAX - a)) {
return 0u; /* overflow: return error */
}
*result = a + b;
return 1u; /* success */
}
/* CERT INT32-C: Ensure signed integer operations do not overflow */
/* Signed overflow is undefined behaviour in C */
int32_t safe_add_i32(int32_t a, int32_t b, int32_t *result)
{
if (((b > 0) && (a > (INT32_MAX - b))) ||
((b < 0) && (a < (INT32_MIN - b)))) {
return 0; /* overflow detected */
}
*result = a + b;
return 1;
}
/* CERT INT31-C: Ensure integer conversions do not lose data/sign */
/* Unsafe: */
int32_t big = 100000;
uint8_t small_unsafe = (uint8_t)big; /* truncates to 160 — wrong! */
/* Safe: check before converting */
uint8_t to_u8_safe(int32_t val) {
if ((val < 0) || (val > 255)) {
/* handle range error */
return 0u;
}
return (uint8_t)val;
} Memory Security Rules
#include
#include
/* CERT STR31-C: Guarantee that storage for strings has sufficient space
Vulnerable: strcpy without bounds check */
void unsafe_copy(char *dst, const char *src) {
strcpy(dst, src); /* VULNERABLE: src may be longer than dst */
}
/* Safe: use strncpy with explicit length limit */
void safe_copy(char *dst, size_t dst_size, const char *src) {
if ((dst == NULL) || (src == NULL) || (dst_size == 0u)) { return; }
strncpy(dst, src, dst_size - 1u); /* leave room for null terminator */
dst[dst_size - 1u] = ' '; /* explicitly null-terminate */
}
/* CERT ARR30-C: Prevent array index out of bounds */
#define DID_TABLE_SIZE 32u
typedef void (*DidHandler_t)(void);
static DidHandler_t g_did_handlers[DID_TABLE_SIZE];
void call_did_handler(uint8_t did_index) {
/* Unsafe: no bounds check */
/* g_did_handlers[did_index](); */ /* if did_index >= 32 → out of bounds */
/* Safe: check before access */
if ((did_index < DID_TABLE_SIZE) && (g_did_handlers[did_index] != NULL)) {
g_did_handlers[did_index]();
}
}
/* CERT MEM35-C: Allocate sufficient memory for object */
/* In embedded: prefer static allocation; no malloc/free in ASIL code */ Summary
CERT-C complements MISRA-C by focusing on exploitability: an integer overflow that MISRA flags as undefined behaviour might also be a CERT INT32-C violation that is exploitable if the overflow result is used to size a buffer allocation. For AUTOSAR Adaptive Platform and connected ECUs (ISO/SAE 21434), CERT-C compliance is increasingly required alongside MISRA-C. The highest-impact CERT-C rules for automotive embedded code: INT30-C (unsigned wrapping), ARR30-C (array bounds), and STR31-C (string buffer sizing) — the three most common classes of remotely exploitable vulnerabilities.
🔬 Deep Dive — Core Concepts Expanded
This section builds on the foundational concepts covered above with additional technical depth, edge cases, and configuration nuances that separate competent engineers from experts. When working on production ECU projects, the details covered here are the ones most commonly responsible for integration delays and late-phase defects.
Key principles to reinforce:
- Configuration over coding: In AUTOSAR and automotive middleware environments, correctness is largely determined by ARXML configuration, not application code. A correctly implemented algorithm can produce wrong results due to a single misconfigured parameter.
- Traceability as a first-class concern: Every configuration decision should be traceable to a requirement, safety goal, or architecture decision. Undocumented configuration choices are a common source of regression defects when ECUs are updated.
- Cross-module dependencies: In tightly integrated automotive software stacks, changing one module's configuration often requires corresponding updates in dependent modules. Always perform a dependency impact analysis before submitting configuration changes.
🏭 How This Topic Appears in Production Projects
- Project integration phase: The concepts covered in this lesson are most commonly encountered during ECU integration testing — when multiple software components from different teams are combined for the first time. Issues that were invisible in unit tests frequently surface at this stage.
- Supplier/OEM interface: This is a topic that frequently appears in technical discussions between Tier-1 ECU suppliers and OEM system integrators. Engineers who can speak fluently about these details earn credibility and are often brought into critical design review meetings.
- Automotive tool ecosystem: Vector CANoe/CANalyzer, dSPACE tools, and ETAS INCA are the standard tools used to validate and measure the correct behaviour of the systems described in this lesson. Familiarity with these tools alongside the conceptual knowledge dramatically accelerates debugging in real projects.
⚠️ Common Mistakes and How to Avoid Them
- Assuming default configuration is correct: Automotive software tools ship with default configurations that are designed to compile and link, not to meet project-specific requirements. Every configuration parameter needs to be consciously set. 'It compiled' is not the same as 'it is correctly configured'.
- Skipping documentation of configuration rationale: In a 3-year ECU project with team turnover, undocumented configuration choices become tribal knowledge that disappears when engineers leave. Document why a parameter is set to a specific value, not just what it is set to.
- Testing only the happy path: Automotive ECUs must behave correctly under fault conditions, voltage variations, and communication errors. Always test the error handling paths as rigorously as the nominal operation. Many production escapes originate in untested error branches.
- Version mismatches between teams: In a multi-team project, the BSW team, SWC team, and system integration team may use different versions of the same ARXML file. Version management of all ARXML files in a shared repository is mandatory, not optional.
📊 Industry Note
Engineers who master both the theoretical concepts and the practical toolchain skills covered in this course are among the most sought-after professionals in the automotive software industry. The combination of AUTOSAR standards knowledge, safety engineering understanding, and hands-on configuration experience commands premium salaries at OEMs and Tier-1 suppliers globally.