Live briefing
Everything about Memory corruption
Type of software bug
Memory corruption occurs in a computer program when the contents of a memory location are modified due to programmatic behavior that exceeds the intention of the original programmer or program/language constructs; this is termed as violation of memory safety. The most likely causes of memory corruption are programming errors. When the corrupted memory contents are used later in that program, it leads either to program crash or to strange and bizarre program behavior. Nearly 10% of application crashes on Windows systems are due to heap corruption. Wikipedia →
🧭 Start here: a 6-step reading path
- Read the overview: Memory corruptionA 5-minute orientation
- Skim a recent paper: Wemby’s Web: Hunting for Memory Corruption in WebAssemblyInfluential work since 2022
- Pick up a classic book: Financial ManagementThe most-reprinted book on the subject
- Read the landmark paper: River and the corruption of memoryCited 24 times
- Go sideways: Memory safetyA closely related topic
- Go sideways: Buffer overflowA closely related topic
📖 Definitions
No dictionary entry for this exact phrase.
🗂️ The subject at a glance
No outline available.
🏆 Landmark papers (most cited)
River and the corruption of memory
Discovery and Identification of Memory Corruption Vulnerabilities on Bare-Metal Embedded Devices
A Survey on Thwarting Memory Corruption in RISC-V
Anatomy of Memory Corruption Attacks and Mitigations in Embedded Systems
A unit-based symbolic execution method for detecting memory corruption vulnerabilities in executable codes
ovAFLow: Detecting Memory Corruption Bugs with Fuzzing-Based Taint Inference
Mitigation of Kernel Memory Corruption Using Multiple Kernel Memory Mechanism
Dopamine affects short-term memory corruption over time in Parkinson’s disease
🆕 Influential since 2022
Wemby’s Web: Hunting for Memory Corruption in WebAssembly
Capturing Invalid Input Manipulations for Memory Corruption Diagnosis
Memory Corruption at the Border of Trusted Execution
When Memory Corruption Met Concurrency: Vulnerabilities in Concurrent Programs
Mechanisms underlying corruption of working memory in Parkinson's disease
📚 Books worth reading
- 📕Financial ManagementUnited States. General Accounting Office · 1987
The simple truthDavid Baldacci · 1998
The ReckoningMary L. Trump · 2021
Force and Contention in Contemporary ChinaThaxton, Ralph A., Jr. · 2016
Fireheart TigerAliette de Bodard · 2021
La década de la antipolíticaCarlos Iván Degregori · 2000- 📕Tailings of Warren PeaceStephen Law · 2013
ZAWLBUK LEH BIAK INGospel Hrilvelthanga · 2010
Ranked by number of editions on Open Library, a rough measure of how lasting a book is.
🔗 Related topics
- Memory safety Memory safety is the state of being protected from various software bugs and security vulnerabilities when dealing with memory access, such as buffer overflows…
- Buffer overflow In programming and information security, a buffer overflow or buffer overrun is a bug whereby a program writes data to a buffer beyond the buffer's allocated…
- Out-of-bounds read In computer security and programming, an out-of-bounds read is a software anomaly where a program, while reading data from a buffer, reads outside of the…
- Buffer overflow protection Buffer overflow protection is any of various techniques used during software development to enhance the security of executable programs by detecting buffer…
- Segmentation fault In computing, a segmentation fault (often shortened to segfault) or access violation is a failure condition raised by hardware with memory protection,…
- Heap overflow A heap overflow, heap overrun, or heap smashing is a type of buffer overflow that occurs in the heap data area. Heap overflows are exploitable in a different…
- Code sanitizer A code sanitizer is a programming tool that detects bugs in the form of undefined or suspicious behavior by a compiler inserting instrumentation code at…
- Stack buffer overflow In software, a stack buffer overflow or stack buffer overrun occurs when a program writes to a memory address on the program's call stack outside of the…