Hacking and Securing C++
summary
A simple microcontroller embedded device playground is used with a custom one‑byte‑type serial protocol to demonstrate concrete failures: uninitialized stack buffers leak a prior login password in a temperature message leak, freeing-but-not-nulling a heap buffer enables a use-after-free login bypass, and a stack overflow lets attackers hijack return addresses for code execution via return-oriented programming. Demos compile and run; fixes shown include initialization, RAII/smart pointers, secure memory wiping caveats, non‑executable stack and ASLR where available.
AI-written summary · about
chapters (9)
- 0:00Hacking and securing C++
- 1:48Presentation setup and goals
- 8:51Memory model and endianness
- 10:41Stack behavior and vulnerabilities
- 21:20Heap allocation and dangling pointers
- 26:17Buffer overflows and control flow hijacking
- 41:31Mitigating with ASLR
- 54:10Best practices and C++ usage
- 55:36Q&A
related talks
01h 00m“Secure Coding Best Practices: Your First Line Is The Last Line Of Defense (1 of 2)”
17mEmbedded Security's Weakest Link: Lessons From Simple Mistakes
01h 06mSecurity Beyond Memory Safety - Using Modern C++ to Avoid Vulnerabilities by Design
39mBackdooring Hardware Devices by Injecting Malicious Payloads on Microcontrollers
14mEmbedded C and C++: A Security Perspective
33mEmbedded Device Exploitation 101: An Introduction to Firmware Hacking
44mDebugging memory corruptions in C++
01h 34mA Little Introduction to Control Flow Integrity in C++