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

LLVM's 'RFC: C++ Buffer Hardening' at Google

bughunters.google.com | blog | #memory-safety | #secure-coding | #google | #llvm | #cpp | #buffer-hardening | #compiler
📄 Raw .md⬇️ Download .md🔗 Original ↗

Summary

Google shares how it evaluated LLVM's proposed C++ buffer hardening approach, outlining initial conclusions, practical adoption tips, and the next steps planned in this hardening journey.
Published
Collected

Related coverage

blog · bughunters.google.com
Scaling Memory Safety: AI-Assisted Rewrites of C/C++ Dependencies to Rust
This coverage gives security teams current context for monitoring, validation, and remediation.
blog · blog.trailofbits.com
Typos that omit security features and how to test for them
An audit found a typo that silently disabled _FORTIFY_SOURCE; the team found and fixed twenty similar C/C++ bugs on GitHub and shows how to test builds for this missed mitigation.
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 · netspi.com
Rust’s Role in Embedded Security
Rust improves memory safety in embedded systems, eliminating entire vulnerability classes, but logic, hardware, and cryptographic flaws still demand rigorous security testing.
blog · osec.io
Compiler bug causes compiler bug: how a 12-year-old g++ bug took down Solidity
OtterSec explains how a 12-year-old G++ overload-resolution bug, C++20 comparison rewrites and legacy Boost code crash Solidity's compiler (solc) on valid code — and how to fix it.
blog · osec.io
Solidity compilers: memory safety
OtterSec explores the Solidity compilation pipeline and YUL optimizer assumptions to explain what 'memory-safe' assembly actually guarantees — and where inline assembly breaks those guarantees.
Back