Re:Viable ROP-free roadmap for i386/armv8/riscv64/alpha/sparc64
by saagarjha on Tuesday September 26, 2023 @12:23PM
(#37661642)
This misses the point of how ROP works, and is in fact why previous attempts at ROP gadget reduction were flawed: it only takes a handful of gadgets to make a chain. Trying to protect control flow requires more sound approaches than this.
[ Parent
| on HN ]
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...
Re:Viable ROP-free roadmap for i386/armv8/riscv64/alpha/sparc64
by tedunangst on Tuesday September 26, 2023 @04:03PM
(#37665100)
At the time, Todd was testing with whatever the popular rop compiler was, and it wasn't able to chain anything using libc. Even on amd64 you can restrict which gadgets are available. Maybe you can find other approaches with a careful hand search, but I think knocking out the biggest exploit generator is hardly flawed in a practical sense.
Re:Viable ROP-free roadmap for i386/armv8/riscv64/alpha/sparc64
by saagarjha on Tuesday September 26, 2023 @06:17PM
(#37666517)
People don't generate exploits using popular ROP compilers.
Re:Viable ROP-free roadmap for i386/armv8/riscv64/alpha/sparc64
by beachhead on Tuesday September 26, 2023 @07:30PM
(#37667352)
what are popular ROP compilers used for then?
Re:Viable ROP-free roadmap for i386/armv8/riscv64/alpha/sparc64
by saagarjha on Tuesday September 26, 2023 @08:37PM
(#37668073)
CTF challenges mostly
Re:Viable ROP-free roadmap for i386/armv8/riscv64/alpha/sparc64
by beachhead on Tuesday September 26, 2023 @08:59PM
(#37668277)
so they're used in combination with already known exploits but you're saying no one uses them during the development of exploits?
Re:Viable ROP-free roadmap for i386/armv8/riscv64/alpha/sparc64
by saagarjha on Wednesday September 27, 2023 @02:14AM
(#37670829)
No, they’re mostly toys and demos. They’re not an accurate representation of real-world exploit development.
Re:Viable ROP-free roadmap for i386/armv8/riscv64/alpha/sparc64
by beachhead on Wednesday September 27, 2023 @01:16PM
(#37677876)
oh i must be confused about what a CTF challenge is
Re:Viable ROP-free roadmap for i386/armv8/riscv64/alpha/sparc64
by saagarjha on Thursday September 28, 2023 @03:43AM
(#37686546)
CTF challenges are to cooking competitions what exploit development is to being a restaurant cook. There are time limits, practicality is less of a concern, and everyone knows that toy constraints are added because nobody wants to watch you stare at IDA for three weeks