Skip to content

Another motivation for CFG: return-oriented programming #75753

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Aug 22, 2020
Merged

Another motivation for CFG: return-oriented programming #75753

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
6fca004
Another motivation for CFG: return-oriented programming
koutheir Aug 20, 2020
5673b0e
Switched ROP link to Desktop layout instead of mobile layout
koutheir Aug 21, 2020
ec9657a
Fixed a typo
koutheir Aug 21, 2020
8ae3384
Added link to Microsoft's documentation of CFG
koutheir Aug 21, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion src/doc/unstable-book/src/compiler-flags/control-flow-guard.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,8 +19,9 @@ CFG functionality is completely implemented in the LLVM backend and is supported

## When to use Control Flow Guard

The primary motivation for enabling CFG in Rust is to enhance security when linking against non-Rust code, especially C/C++ code. To achieve full CFG protection, all indirect calls (including any from Rust code) must have the appropriate CFG checks, as added by this flag. CFG can also improve security for Rust code that uses the `unsafe` keyword
The primary motivation for enabling CFG in Rust is to enhance security when linking against non-Rust code, especially C/C++ code. To achieve full CFG protection, all indirect calls (including any from Rust code) must have the appropriate CFG checks, as added by this flag. CFG can also improve security for Rust code that uses the `unsafe` keyword.

Another motivation behind CFG is to harden programs against [return-oriented programming (ROP)](https://en.m.wikipedia.org/wiki/Return-oriented_programming) attacks. CFG disallows an attacker from taking advantage of the programs own instructions while redirecting control flow in unexpected ways.

## Overhead of Control Flow Guard

Expand Down