SQ14123
Detected Windows executable files that might ineffectively implement CFG vulnerability mitigation protection.
| priority | CI/CD status | severity | effort | RL level | RL assessment |
|---|---|---|---|---|---|
| None | pass | low | high | None | None |
About the issue
Control Flow Guard (CFG/CFI) protects the code flow integrity by ensuring that dynamic calls are made only to vetted functions. This mitigation is detected as enabled, but its effectiveness is impacted by unexpected function alignment. For optimal protection, guarded functions must be aligned to the 16-byte boundary. Any misalignment leaves a small window for the malicious code to take advantage of an improperly secured code flow path.
How to resolve the issue
- There are currently no programming language toolchain options to force proper function alignment. If this warning is issued for a file, it is likely that a future build, with some code changes, will make the compiler order the application code differently and eliminate the CFG coverage gaps.
Incidence statistics
ReversingLabs periodically collects and analyzes the contents of popular software package repositories for threat research purposes.
For every repository, the chart shows the percentage of projects that triggered the software assurance policy. In other words, it shows how many projects were found to have the specific issue described on this page.
The percentages are calculated from the total amount of packages analyzed:
- RubyGems: 174K
- Nuget: 189K
- PyPi: 403K
- NPM: 2.1M
Recommended reading
- Control-flow integrity (External resource - MaskRay)
- Control Flow Guard for platform security (External resource - Microsoft)