That's a lot of words for a pretty basic explanation of how to exploit kernel that has a very specific kind of bug: "option length" parser error in TCP frames that leads to user-controlled stack overwrite.
Which kernel is it is unclear. There are zero details in the paper, not even which OS is this (Linux? Windows? Some BSD?). There are no mentions of ASLR, stack protectors or any other security mechanisms either.
In fact, there is nothing novel in the paper at all. I suspect author spent too much time with AI.
This is just some random raw socket code which mentions scary words (EXPLOITS!!!) but actually does not contain any working exploits.
And you still haven't answered my question - that vulnerabile code that you plan to exploit, does it exist anywhere yet? Or is the whole thing something you made up?
theamk•2w ago
Which kernel is it is unclear. There are zero details in the paper, not even which OS is this (Linux? Windows? Some BSD?). There are no mentions of ASLR, stack protectors or any other security mechanisms either.
In fact, there is nothing novel in the paper at all. I suspect author spent too much time with AI.
KaoruAK•2w ago
theamk•2w ago
And you still haven't answered my question - that vulnerabile code that you plan to exploit, does it exist anywhere yet? Or is the whole thing something you made up?