News for hackers. Stuff that matters.
Re:Viable ROP-free roadmap for i386/armv8/riscv64/alpha/sparc64 by Joker_vD on Tuesday September 26, 2023 @01:01PM (#37662331)
Say, if hardware checked that RET transfers control to a place that's immediately preceded by a CALL instruction, would that help?
Re:Viable ROP-free roadmap for i386/armv8/riscv64/alpha/sparc64 by IshKebab on Tuesday September 26, 2023 @01:40PM (#37662949)
ARM's Branch Target Identification does something similar to that (but for jumps & calls, not returns).
Re:Viable ROP-free roadmap for i386/armv8/riscv64/alpha/sparc64 by saagarjha on Tuesday September 26, 2023 @01:32PM (#37662836)
It would help but it wouldn’t solve ROP. I think it would probably be less useful than gadget reduction, honestly, since there are a lot of useful sequences after a call instruction.
Re:Viable ROP-free roadmap for i386/armv8/riscv64/alpha/sparc64 by deadbeeves on Tuesday September 26, 2023 @01:22PM (#37662679)
That would disable certain mechanisms that are occasionally useful. For example, to implement user-mode context switches and function hooking.
Re:Viable ROP-free roadmap for i386/armv8/riscv64/alpha/sparc64 by cryptonector on Tuesday September 26, 2023 @03:07PM (#37664325)
A shadow stack of return addresses would help.
Re:Viable ROP-free roadmap for i386/armv8/riscv64/alpha/sparc64 by hovav on Wednesday September 27, 2023 @11:59PM (#37685095)
It would not help at all. See (all of, but especially) section 5.4 of N. Carlini, A. Barresi, M. Payer, D. Wagner, and T.R. Gross, "Control-Flow Bending: On the Effectiveness of Control-Flow Integrity," in proc. USENIX Security 2015, https://www.usenix.org/conference/usenixsecurity15/technical...