The Problem with Dynamic Program Analysis
blog.trailofbits.com | blog | #memory-safety | #use-after-free | #tools | #vulnerability-discovery | #static-analysis | #llvm | #program-analysis | #data-flow | #pointsto | #data-flow-analysis
Summary
Dynamic tools like AddressSanitizer only check executed paths; Trail of Bits' PointsTo applies whole-program static data-flow analysis on LLVM bitcode to find use-after-free bugs at scale.
- Published
- Collected
--- id: 2393 title: "The Problem with Dynamic Program Analysis" source_domain: blog.trailofbits.com source_url: "https://blog.trailofbits.com/2016/03/09/the-problem-with-dynamic-program-analysis/" published_at: "2016-03-09T18:53:34Z" tags: ["memory-safety", "use-after-free", "tools", "vulnerability-discovery", "static-analysis", "llvm", "program-analysis", "data-flow", "pointsto", "data-flow-analysis"] phying_url: "https://phying.com/item/2393" lang: en --- # The Problem with Dynamic Program Analysis ## Summary Dynamic tools like AddressSanitizer only check executed paths; Trail of Bits' PointsTo applies whole-program static data-flow analysis on LLVM bitcode to find use-after-free bugs at scale. ## Intelligence Metadata - **Sources:** blog.trailofbits.com - **Published:** 2016-03-09T18:53:34Z - **Original:** https://blog.trailofbits.com/2016/03/09/the-problem-with-dynamic-program-analysis/ - **Phying News:** https://phying.com/item/2393