Paper frames code-reuse attacks that persist in memory-safe languages
Original title: Memory Safety Isn't All You Need: Code Reuse Attacks in Memory Safe Languages
Object injection, prototype and class pollution, DOM clobbering, and DOM script gadgets share a weakness-plus-gadget structure.
The paper argues that memory safety blocks classical corruption-based code reuse but not attacks such as object injection, prototype pollution, class pollution, DOM clobbering, and DOM script gadgets. It models them as attacker-controlled data influencing a fetch from shared runtime state, followed by a gadget that carries the fetched value to a sensitive sink. It derives weakness and gadget types, groups defenses as mediation, minimization, and constraint, and sketches a model language for formal conditions.
- The framework captures five established attack classes in memory-safe languages.
- Weakness types are stateless, mutating, and recycling.
- Gadget structures are simple, vertical, and horizontal.
- Candidate defenses are derived from mediation, minimization, and constraint.
From the original article
1 min read at arxiv.orgMemory safety rules out classical code reuse attacks that rely on arbitrary memory corruption, but does not eliminate code reuse altogether. Attacks such as object injection, prototype pollution, class pollution, DOM clobbering, and DOM script gadgets arise in memory-safe languages without violating the underlying memory safety abstraction.
By Eric Cornelissen · arxiv.org
A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.