No Leak, No Problem – Bypassing Aslr with a Rop Chain to Gain Rce
Postedabout 2 months agoActiveabout 2 months ago
modzero.comTechstory
calmmixed
Debate
60/100
Exploit DevelopmentAslr BypassEmbedded Systems Security
Key topics
Exploit Development
Aslr Bypass
Embedded Systems Security
The post describes a ROP chain exploit to gain RCE on an embedded device, sparking discussion on the effectiveness of ASLR and other security measures in such systems.
Snapshot generated from the HN discussion
Discussion Activity
Light discussionFirst comment
3h
Peak period
2
5-6h
Avg / period
1.1
Comment distribution8 data points
Loading chart...
Based on 8 loaded comments
Key moments
- 01Story posted
Nov 14, 2025 at 6:39 PM EST
about 2 months ago
Step 01 - 02First comment
Nov 14, 2025 at 9:55 PM EST
3h after posting
Step 02 - 03Peak activity
2 comments in 5-6h
Hottest window of the conversation
Step 03 - 04Latest activity
Nov 15, 2025 at 11:24 AM EST
about 2 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
ID: 45933497Type: storyLast synced: 11/20/2025, 8:00:11 PM
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
I would not consider this actually bypassing ASLR, because ASLR is already turned off for a critically important block of code. Practically any large-enough binary has gadgets that can be useful for ROP exploitation, even if chaining them together is somewhat painful. For ASLR to be a reasonably effective mitigation, every memory region needs to be randomized.
It’s a matter of opinion I guess. In the early days of ASLR it was common to look for modules that were not position independent for your ROP chain and that process was probably called bypassing aslr. These days we’d probably just call that not being protected by aslr.
It’s fun working on targets with a less established research history. And I love a soup to nuts writeup, Thanks.
Expanding it, perhaps to the benefit of others like me.
Also not familiar at all with the checksec program, but from my look at the documentation, you expect to see PIE enabled not DSO (which implies dynamic shared object).
3 more comments available on Hacker News