|
|
Subscribe / Log in / New account

Comparing GCC and Clang security features

Comparing GCC and Clang security features

Posted Sep 13, 2019 11:58 UTC (Fri) by nix (subscriber, #2304)
Parent article: Comparing GCC and Clang security features

FYI: finegrained forward-edge CFI verifies that indirect jumps go to a function with the right prototype. (An even finer-grained mode could be imagined that validates that at least some indirect calls for which this sort of thing is statically computable call only those functions which it is known that it is possible for that call-site to indirectly call, ruling out even some functions with the right prototype. A good intermediate state might be able to rule out indirect calls to functions whose address is never taken, even if they have the right prototype. Since most functions' addresses are never taken, this might reduce the set of ROP gadgets significantly.)


to post comments

Comparing GCC and Clang security features

Posted Sep 13, 2019 15:40 UTC (Fri) by sami (subscriber, #4163) [Link]

> A good intermediate state might be able to rule out indirect calls to functions whose address is never taken

Clang's CFI implementation does exactly this.


Copyright © 2025, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds