"we had a good thing, you stupid son of a bitch! we had Lows. we had Mediums. we had renderer RCE bonuses, and it all ran like clockwork! you could have shut your mouth, let your fuzzers run, and made as much money as you ever needed! it was perfect! but no, you just HAD to go and flood the team with your AI-hallucinated slop reports"
@cr4zyengineer@m1thr1da@realpastaya i might have been angry for nothing and I am sorry but my point stands: why would you lie about it being a bof ? it doesn’t make sense. Sorry again for the previous tweet 😛
@cr4zyengineer@m1thr1da@realpastaya why would you lie about such thing ? Buffer overflow in a discord bot ? Cmon man wtf… + saying “my kernel research paid off” when you’re just reusing a token - what is wrong with you ?
@guime_guimeLove@5mukx From what I read from the writeup it appears that the sRIP offset is <1000 so the buffer’s size isn’t 1000 bytes (which doesn’t make sense regarding the check i agree)
@T3chFalcon IMAGINE 😭😭 focusing on the delivery instead of the lesson 🧠✨
Like… argue with the MESSAGE, not the font, the tone, the vibes, the commas 😭💀
If it made you think, it already WON 🏆🔥
🎄 New Root-Xmas Challenge 🎄
✨Today, heap your skills and parse your way through Santa’s picture-perfect surprises!
📌Submitted by : Numb3rs
🔗Details & participation here: https://t.co/a9mhshchcy
Good luck to you all !🎅
@NaMi____NaMi@popovicu94 This is how SROP works. We make a segfault so that we can control the state in which the kernel is gonna put the process after the signal.
@JDG_1980@robertgraham this could be a never ending debate and i don’t care that much but those mitigations can be bypassed + i don’t see how the end-user would accept using a software that is vulnerable to such a strong primitive (for this specific vuln)
You just got a black box target and zero context.
Where do you even begin?
Here’s my take after two years in vuln research - what actually matters, and what’s just noise 👇
https://t.co/qtX4QJyc8c