You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As suggested by @thejh, separating allocations where the compiler can prove that the allocation is fixed-size from the other allocations makes it a bit harder for attacker to exploit UAF, due to object size constrains.
This technique only makes sense when isoalloc isn't used via LD_PRELOAD or in a separate library of course.
The text was updated successfully, but these errors were encountered:
I spent some time trying to implement this but ultimately was not able to get clangs __builtin_constant_p to work correctly within iso_alloc() even when compiling sources directly. Can revisit this if you have a PoC?
As suggested by @thejh, separating allocations where the compiler can prove that the allocation is fixed-size from the other allocations makes it a bit harder for attacker to exploit UAF, due to object size constrains.
This technique only makes sense when isoalloc isn't used via
LD_PRELOAD
or in a separate library of course.The text was updated successfully, but these errors were encountered: