Small correction: As far as I know, JIT compilation is possible (and even done) in a way where the memory isn't writable and executable at the same time, but first writable and then (after JIT compilation) readable and executable.
It makes sense to me that data would be executable by default. Code is just another form of data (assembly opcodes are just numbers after all). Unless you dedicate memory or circuitry to it, the only obvious way to know whether a program is reading code or data is by essentially setting some kind of flag in the program and update it whenever a program starts or ends - to keep track of whether the program saw a "start of executable section" or "end of execution" section. It would be expensive to check every single byte between the current and target locations before executing a jump, so all we can do is put it in the normal program code. Its unsurprising that an exploit that alters program control can be used to skip over part of the program control process.
Cheers for explaining DEP from a historical standpoint. No one talks about the stack being executable in 2024, so I was pretty confused as to what DEP was doing when only .text has execution rights anyway.
in OpenBSD, I think this is the W^X feature where a memory location is exclusively either writable or executable, so once a memory location is writable, it will never be executable
Difficult to understand. I found this term while looking for correcting a solution on GIMP. If you open the picture on both GIMP and a photo viewer program, GIMP will crash. It says that DEP may be the cause. I don't wanted to upgrade to W10 right now. I wonder why this will be linked because picture can't trigger the buffer (except if a code was injected on the meta data with cmd prompt)
Small correction: As far as I know, JIT compilation is possible (and even done) in a way where the memory isn't writable and executable at the same time, but first writable and then (after JIT compilation) readable and executable.
Glad I found this channel, hope you will make more videos in the future!
Incredible video! You just explained a difficult topic in minutes. Amazing work!
This was helpful. Thanks!
Great video! This channel really deserves more views
Great explanation
Thank you. Really good explanation!
It is very nice channel, respect for your work.
your videos are so great miss you lots hope SF has been fannnTASTIC!
It makes sense to me that data would be executable by default. Code is just another form of data (assembly opcodes are just numbers after all). Unless you dedicate memory or circuitry to it, the only obvious way to know whether a program is reading code or data is by essentially setting some kind of flag in the program and update it whenever a program starts or ends - to keep track of whether the program saw a "start of executable section" or "end of execution" section. It would be expensive to check every single byte between the current and target locations before executing a jump, so all we can do is put it in the normal program code. Its unsurprising that an exploit that alters program control can be used to skip over part of the program control process.
thank you! this is the only short vid for us lay people, concise and friendly
thank you!! you just save my exam tomorrow!!!
Cheers for explaining DEP from a historical standpoint. No one talks about the stack being executable in 2024, so I was pretty confused as to what DEP was doing when only .text has execution rights anyway.
Really great video!
Thank you!
Excellent content, please make more
no way man youre covering all the topics I wanna know about legend
I really like the animation! Keep up the good work.
Thanks, will do!
that was very clear, thank you. Would be cool to see a video from you on ROP
in OpenBSD, I think this is the W^X feature where a memory location is exclusively either writable or executable, so once a memory location is writable, it will never be executable
Difficult to understand. I found this term while looking for correcting a solution on GIMP. If you open the picture on both GIMP and a photo viewer program, GIMP will crash.
It says that DEP may be the cause. I don't wanted to upgrade to W10 right now. I wonder why this will be linked because picture can't trigger the buffer (except if a code was injected on the meta data with cmd prompt)
Stack execution was used back in the day for self modifying code which is seen as bad nowadays.
THANK YOU!
bro please make more videooosssssssssss