PPhying中文
Curated security research, vulnerabilities, advisories and tools for practitioners.

The future of Clang-based tooling

blog.trailofbits.com | blog | #tooling | #static-analysis | #llvm | #compiler | #trail-of-bits | #program-analysis | #compilers | #clang | #data-flow
📄 Raw .md⬇️ Download .md🔗 Original ↗

Summary

Peter Goodman examines why Clang dominates compiling yet disappoints toolsmiths: its AST, CFG, and libClang interfaces hide crucial data-flow connections, and new tooling aims to fill these gaps.
Published
Collected

Related coverage

blog · blog.trailofbits.com
Let’s talk about CFI: clang edition
Trail of Bits explains Control Flow Integrity with clang 3.9: what CFI mitigations like cfi-icall and cfi-vcall enforce, their limitations, and the -flto plus -fsanitize=cfi build flags required.
blog · blog.trailofbits.com
Using Static Analysis and Clang To Find Heartbleed
Trail of Bits built a Clang analyzer plugin that statically detects Heartbleed-style bugs: it taints ntohl/ntohs return values and flags unconstrained data used as memcpy sizes, tested on OpenSSL.
research · blog.quarkslab.com
Clang Hardening Cheat Sheet - Ten Years Later
Quarkslab updates its Clang Hardening Cheat Sheet a decade later with OpenSSF-recommended flags and newer mitigations against memory corruption, ROP/JOP and speculative execution attacks.
research · blog.quarkslab.com
Implementing a Custom Directive Handler in Clang
How-to on implementing a custom #pragma directive handler in clang, used to drive an LLVM-based obfuscator while keeping sources compilable elsewhere; a tour of the preprocessing and parsing stages.
research · blog.quarkslab.com
SCAF - Source Code Analysis Framework based on Clang - Pre-alpha preview
A preview of SCAF, a Clang-based source code analysis framework: a Python API and GUI that store ASTs and metadata in a shared database, plus a make-process hook for accurate build context.
research · blog.quarkslab.com
A glance at compiler internals: Keep my memset
Why Clang/LLVM can delete your memset: tracing llvm.memset through Dead Store Elimination, the risk for code that wipes secrets, and the volatile function-pointer trick that keeps the wipe alive.
Back