SQ14132
Detected Windows executable files that do not implement Intel CET vulnerability mitigation protection.
| priority | CI/CD status | severity | effort | RL level | RL assessment |
|---|---|---|---|---|---|
| None | pass | medium | medium | None | None |
About the issue
Intel Control-flow Enforcement Technology (CET) protects the code flow integrity by ensuring that indirect calls are made only to vetted functions, and that the functions return only to their respective callers. This mitigation protects dynamically resolved function targets by instrumenting the code responsible for transferring execution control. It is implemented at the hardware level, but the applications need to opt in. Special processor instructions are implemented to track indirect branch execution, while the function returns are verified through the use of a shadow stack. Any deviation from the known and trusted code flow paths will cause the application to terminate. This makes malicious code less likely to execute.
How to resolve the issue
- It's highly recommended to enable this option for all software components used at security boundaries, or those that process user controlled inputs.
- To enable this mitigation, refer to your programming language toolchain documentation.
- In Microsoft VisualStudio, you can enable CET mitigation by passing the /CETCOMPAT parameter to the linker.
Incidence statistics
Not relevant for this type of issue.
Recommended reading
- A Technical Look at Intel’s Control-flow Enforcement Technology (External resource - Intel)
- Control-flow integrity (External resource - MaskRay)
- Shadow stack (External resource - NIST)