The bibliographic entry was discovered and compiled by a machine, and published without a person checking it against the publication. The publication itself is the authors' own work — this badge says nothing about it.
Just-In-Time Code Reuse: On the Effectiveness of Fine-Grained Address Space Layout Randomization
From OpenAlex, which stores abstracts as an
index of words and their positions: what is shown is rebuilt from that,
and reads fluently whether or not it is what the author wrote.
Abstract
Fine-grained address space layout randomization (ASLR) has recently been proposed as a method of efficiently mitigating runtime attacks. In this paper, we introduce the design and implementation of a framework based on a novel attack strategy, dubbed just-in-time code reuse, that undermines the benefits of fine-grained ASLR. Specifically, we derail the assumptions embodied in fine-grained ASLR by exploiting the ability to repeatedly abuse a memory disclosure to map an application's memory layout on-the-fly, dynamically discover API functions and gadgets, and JIT-compile a target program using those gadgets -- all within a script environment at the time an exploit is launched. We demonstrate the power of our framework by using it in conjunction with a real-world exploit against Internet Explorer, and also provide extensive evaluations that demonstrate the practicality of just-in-time code reuse attacks. Our findings suggest that fine-grained ASLR may not be as promising as first thought.
How it got here
How it got here
agent via openalex
Added
2026-10-25 20:40 UTC
Not denied by
a person 2026-10-29 17:12 UTC
Cite it as
@misc{snow2013justintime,
title = {Just-In-Time Code Reuse: On the Effectiveness of Fine-Grained Address Space Layout Randomization},
author = {Kevin Z. Snow and Fabian Monrose and Lucas Davi and Alexandra Dmitrienko and Christopher Liebchen and Ahmad‐Reza Sadeghi},
year = {2013},
journal = {Proceedings - IEEE Symposium on Security and Privacy/Proceedings of the ... IEEE Symposium on Security and Privacy},
publisher = {IEEE Computer Society},
pages = {574--588},
doi = {10.1109/sp.2013.45},
}