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

The Art of Detecting Memory Leaks in C++ Applications

hackerone.com | blog | #debugging | #hackerone | #dynamic-analysis | #cpp | #addresssanitizer | #memory-leaks | #valgrind
📄 Raw .md⬇️ Download .md🔗 Original ↗

Summary

HackerOne surveys tools for detecting memory leaks in C++ applications, covering Valgrind Memcheck and AddressSanitizer, and how each pinpoints leaks with stack traces and allocation details.
Published
Collected

Related coverage

blog · blog.trailofbits.com
Understanding AddressSanitizer: Better memory safety for your code
Trail of Bits explains how AddressSanitizer works, covering shadow memory, redzones, container annotations, limitations, and false positives, plus the LLVM contributions these findings produced.
blog · blog.trailofbits.com
Everything You Ever Wanted To Know About Test-Case Reduction, But Didn’t Know to Ask
Alex Groce explains test-case reduction: shrinking failing inputs with tools like the DeepState reducer to speed debugging and cut test overhead, plus six reducers worth knowing.
blog · netspi.com
Attacking Android Applications With Debuggers
Without root, testers can attach a debugger to Android apps after decompiling with APKTool, stepping through method calls to intercept traffic pre-encryption and capture keys never written to disk.
blog · hackerone.com
Measuring The Fix: How We Evaluate Frontier Models on Remediation Quality
HackerOne tested frontier models on security fix quality and found the judge mattered more than the model. See how CTEM remediation earns engineer trust.
blog · hackerone.com
Critical PHP Vulnerabilities: What Security Teams Need to Know
Learn about the critical PHP vulnerabilities, HackerOne’s response, and the rise in reports. Review patching guidance and coordinated disclosure practices.
blog · hackerone.com
Project Glasswing: What We Learned Running a Frontier Model on Our Own Codebase
HackerOne ran Anthropic's Mythos 5 model against its own production code; it surfaced a critical RCE spanning three safe-in-isolation commits, illustrating compositional risk that diff review misses.
Back