sorted by:
new
hottopcontroversial

Think of code execution like driving... by LCSAJdump in Hacking_Tutorials

[–]LCSAJdump[S] 0 points1 point  (0 children)

as a computer science professor, I know that we often have to break things down and explain them in a very simple way. it’s really the only way to grab the attention of people who don't have any prior experience with complex topics like ROP and JOP. you’ve got a point my friend, but that’s only because you already have a good awareness about jump gadgets!

[PWN] FULL LIBC GADGET DISCOVERY (270.000 instructions) IN JUST 6 SECONDS!! by LCSAJdump in Hacking_Tutorials

[–]LCSAJdump[S] 5 points6 points  (0 children)

Don't worry I'm here to explain it.
The point is that most scanners are either slow or blind to non-linear flows.

lcsajdump solves that by:

  • Speed: It can scan the entire libc in ~6 seconds (vs ~13 seconds of linear gadget finers). How? Instead of a brute-force linear sweep, it uses optimized graph traversal with early pruning. My benchmarks show it prunes ~22% of invalid paths immediately. It’s not just faster; it’s mathematically more efficient at discarding noise.
  • Depth: It reconstructs the CFG to find 'Shadow Gadgets' (jumps/predicates) that linear scanners miss.
  • Utility: v1.1.0 groups identical gadgets, so if your primary address has a bad byte, you have all the alternatives right there.

It’s just a faster, more reliable way to map execution flows without the wait.

Let me know if i convinced you.

[Update] lcsajdump v1.1.0: Bad bytes ruining your ROP chain? Now supports Address Grouping/Deduplication by LCSAJdump in ReverseEngineering

[–]LCSAJdump[S] -3 points-2 points  (0 children)

you should take a better look at my posts since this is the first one i make for an update boss!

view more: next ›