News for hackers. Stuff that matters.
Re:Self-modifying code using GCC (2011) by Zambyte on Monday August 07, 2023 @10:38AM (#37035054)
What would a practical application of something like this be? Maybe a JIT compiler that takes advantage of the C stack?
Re:Self-modifying code using GCC (2011) by throwaway073123 on Monday August 07, 2023 @10:57AM (#37035360)
- JIT / optimizing for the host device

- hot patching

- making sure sysadmins have healthy sense of panic available to them at all times

Re:Self-modifying code using GCC (2011) by planede on Monday August 07, 2023 @10:59AM (#37035381)
None, this is wildly undefined behavior, even considering GCC's extension and its documentation. I doubt that GCC implementers would be interested in defining the behavior here.

edit: There might be room for some other extension here, but as an other commenter already wrote:

1. functions might not be contiguous in memory

2. the code that you are moving should better be position independent

So any such extension should handle these issues one way or an other.

Re:Self-modifying code using GCC (2011) by countWSS on Monday August 07, 2023 @11:12AM (#37035579)
Instead of if( condition) then code1: else code2, computed goto will just switch the branch to unconditional jump to either code1/code2, which bypasses branch misprediction penalty and is generally more elegant.
Re:Self-modifying code using GCC (2011) by CarVac on Monday August 07, 2023 @11:38AM (#37035936)
Does that not actually cause a mispredict if the speculative execution happened before the code change?
Re:Self-modifying code using GCC (2011) by messe on Monday August 07, 2023 @11:40AM (#37035968)
Worse. It's more than likely to cause a cache miss, and waiting on memory is going to be even slower than a mispredicted branch.
Re:Self-modifying code using GCC (2011) by monocasa on Monday August 07, 2023 @11:49AM (#37036080)
It could be even worse. I've seen x86 cores where the icache/dcache consistency logic ended up internally being most of a page fault and recovery once noticed by the processor.
Re:Self-modifying code using GCC (2011) by messe on Monday August 07, 2023 @12:33PM (#37036752)
Oof on that note: at least in the example in the article, it's going to cost a TLB miss as page permissions are getting changed. So that's a page-table walk which means %cr3 -> PML4 -> PDPT -> PD -> PT -> the actual address you want to access; potentially up to 5 memory accesses (6 if your system has more than 256TB of RAM and you're using 5-level paging).

That being said, in a loop you'd only take this hit on the first run. You'd be back to cache misses after that.

Re:Self-modifying code using GCC (2011) by slaymaker1907 on Monday August 07, 2023 @01:03PM (#37037261)
> One of my research topics last year was self-modifying code mainly for *obfuscation*.

I think obfuscation is generally a really bad idea, but that was brought up in the article. One practical application for self-modifying code is hotpatching. Sometimes you really don't want to stop the process but want to change the implementation for some function.

Re:Self-modifying code using GCC (2011) by Borg3 on Monday August 07, 2023 @02:12PM (#37038321)
Hold on, How you can actually do hotpatching on x86 protected mode? code is usualy executable but read only. data + stack is usualy NX but writable.
Re:Self-modifying code using GCC (2011) by LegionMammal978 on Monday August 07, 2023 @02:24PM (#37038498)
The processor itself doesn't enforce W^X protection; even though writable pages are NX by convention, nothing inherently stops you from using (the equivalent of) mmap(PROT_READ | PROT_WRITE | PROT_EXEC) and copying the instructions in, or doing the same with existing pages using mprotect(), at which point you can hotpatch as much as you want. Of course, some OSes forbid this as a hardening measure, but allowing it remains very common.
Re:Self-modifying code using GCC (2011) by slaymaker1907 on Monday August 07, 2023 @03:03PM (#37039187)
You do the same thing JIT does and change the permissions on the page to NX, apply whatever update you want, then remove the write permission and make it executable again. Even though it seems like it doesn't make a difference, it's much more difficult for an attacker to change the page permissions than it is for the hotpatcher/JIT. I think this could still fail though depending on how strict your OS is in which case you might need to use explicit function pointers which are obviously writable.

Some systems apparently allow you to add executable without removing write as that is what the OP does with "mprotect(page, getpagesize(), PROT_READ | PROT_WRITE | PROT_EXEC);". However,

Re:Self-modifying code using GCC (2011) by metadat on Monday August 07, 2023 @04:21PM (#37040437)
Why is it more difficult for an attacker to change the code compared the JIT?
Re:Self-modifying code using GCC (2011) by matheusmoreira on Monday August 07, 2023 @09:41PM (#37043414)
Attackers love overflowing buffers but since that memory is not executable they can't put code in there directly. The JIT compiler is almost always the only component which writes to executable pages so they need to somehow trick it into emitting the code they want. It's my understanding that JIT spray attacks are harder to develop.
Re:Self-modifying code using GCC (2011) by matheusmoreira on Monday August 07, 2023 @09:33PM (#37043356)
You can just change the permissions with mprotect.
Re:Self-modifying code using GCC (2011) by onesphere on Monday August 07, 2023 @05:33PM (#37041258)
Computation itself can be seen as self-modifying. Browser loading JS, OS loading DLLs, closures, VMs. It's how "high up the abstraction" you want to go.

I never got into this but "GNU lightning is a free-software library for generating assembly language code at run-time." https://en.wikipedia.org/wiki/GNU_lightning

https://onesphere.hashnode.dev/upstart

And for some reason: https://news.ycombinator.com/item?id=36976878