← Back to context Comment by landr0id 14 hours ago Ask yourself why Mythos was so easily able to develop a remote STACK buffer overflow vulnerability. 2 comments landr0id Reply nozzlegear 13 hours ago Define "so easily"? landr0id 12 hours ago They exploited a linear stack buffer overflow. Not a write-what-where or arb write. A linear stack buffer overflow in 2026! There are at least two distinct failures there:1. No strong stack protectors.2. No kASLR.That's 20-year-old exploit methodology.
nozzlegear 13 hours ago Define "so easily"? landr0id 12 hours ago They exploited a linear stack buffer overflow. Not a write-what-where or arb write. A linear stack buffer overflow in 2026! There are at least two distinct failures there:1. No strong stack protectors.2. No kASLR.That's 20-year-old exploit methodology.
landr0id 12 hours ago They exploited a linear stack buffer overflow. Not a write-what-where or arb write. A linear stack buffer overflow in 2026! There are at least two distinct failures there:1. No strong stack protectors.2. No kASLR.That's 20-year-old exploit methodology.
Define "so easily"?
They exploited a linear stack buffer overflow. Not a write-what-where or arb write. A linear stack buffer overflow in 2026! There are at least two distinct failures there:
1. No strong stack protectors.
2. No kASLR.
That's 20-year-old exploit methodology.