Jump-oriented programming: a new class of code-reuse attack

By Tyler K. Bletsch, Xuxian Jiang, Vincent W. Freeh, Zhenkai Liang. ACM Asia Conference on Computer and Communications Security, 2011

690 citations recorded by the source corpus.

Subfields: Artificial Intelligence, Signal Processing

View Paper: https://www.semanticscholar.org/paper/348b0049b0c7b3f7e74b77cca30213cb7e550360

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

In Artificial Intelligence

In Signal Processing

Citations in the corpus

Data-Oriented Programming: On the Expressiveness of Non-control Data Attacks (2016, background): “Data-oriented gadgets are similar to code gadgets employed in return-oriented programming (ROP) [1], or in jump-oriented programming (JOP) [2].”
Counterfeit Object-oriented Programming: On the Difficulty of Preventing Code Reuse Attacks in C++ Applications (2015, methodology): “Before presenting the ideas and concepts behind COOP in detail, we review the background necessary for understanding our approach and its relation to existing work.”
Code-pointer integrity (2014, background): “Attackers exploit bugs, such as buffer overflows and use after free errors, to cause memory corruption that enables them to steal sensitive data or execute code that gives them control over a remote system [44, 37, 12, 8].”
C-FLAT: Control-Flow Attestation for Embedded Systems Software (2016, background): “Another variant of return-oriented programming are jump-oriented programming attacks [10, 7].”
Out of Control: Overcoming Control-Flow Integrity (2014, methodology): “Nevertheless, it has been shown that ROP is possible in RISC architectures [27], or it can be carried out without using the ret instruction [11], [12] making defenses that are based on the emulation of the ret command less effective [24].”
SoK: Eternal War in Memory (2013, background): “Return-Oriented Programming (ROP) [6], [7], [8], [9], [10], [11], information leaks [12], [13] and the prevalent use of user scripting and just-in-time compilation [14] allow attackers to carry out practically any attack despite all protections.”
Control-Flow Bending: On the Effectiveness of Control-Flow Integrity (2015, background): “Code-reuse attacks are possible when attackerneeded code is already available in the address space of a vulnerable process.”
Hacking in Darkness: Return-oriented Programming against Secure Enclaves (2017, background): “This poses a problem for ROP attacks [8, 9, 32], as the attacker needs to find a vulnerability and gadgets in the victim’s code.”