CyberKit

Control-Flow Integrity

Also called CFI, CFG.

Restricting indirect calls and returns to valid targets only.

What it is

A class of mitigations that constrain a program's indirect branches to a precomputed set of legitimate targets. By validating function-pointer calls and returns, CFI breaks techniques that redirect execution to arbitrary code.

Why it matters

CFI undermines ROP and JOP by rejecting the very jumps those techniques depend on. Knowing whether a target enforced CFI helps gauge how sophisticated a working exploit must have been.

In practice

An exploit's attempt to call into the middle of a function is blocked because that address is not a valid indirect-call target under CFI.

What to look for

  • Binaries built with CFG, CET or CFI enabled.
  • Indirect calls that land outside valid targets.
  • Modules that opt out and weaken the process.

Common mistake

Enabling it in one module only. An unprotected module gives attackers a way around it.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

Read next

Sources