Forging a Microsoft Edge Full Chain with Logic Bugs Only
Posted by austinallegro 11 hours ago
Comments
Comment by darkamaul 8 hours ago
No memory corruptions, no heap shenanigans, just pure logic bugs, almost made easy to understand for the reader.
As a bonus, they also posted a reverse chain: popping Edge from calc [0].
Comment by mschuster91 2 hours ago
What the hell is going on there? Apparently they are spawning new and new and new instances of calc.exe until one random (?) instance is vulnerable to some sort of attack, then they inject some shellcode into it from outside, and manage to trigger it by inputting "1"s until there's an overflow?
Really looking forward to the writeup lol
Comment by its-summertime 9 hours ago
Comment by xnickb 5 hours ago
And it's hard to judge them: I'd also rather focus on real features.
Comment by imtringued 2 hours ago
Special casing your domains to be assumed "secure" is exactly how you build vulnerabilities directly into your software.
It's an inevitable result.
Developers aren't aware because they assume a security model where the special casing is disabled.
Comment by adzm 3 hours ago
Wow, this is disturbing on its own
Comment by MatthiasPortzel 1 hour ago
Comment by antonly 5 hours ago
Comment by layer8 4 hours ago
Comment by deburo 4 hours ago
Comment by akersten 2 hours ago
Comment by tveita 6 hours ago
This is disgusting behaviour, RCE chain or not.
Comment by zhiyan 9 hours ago
Comment by Geezus_42 8 hours ago
Comment by cubefox 7 hours ago
Comment by account42 5 hours ago
Comment by LoganDark 3 hours ago
Comment by cubefox 5 hours ago
Comment by ShinyLeftPad 3 hours ago
Comment by mschuster91 2 hours ago
This entire chain is nothing but a lesson of shame for Microsoft - if you fork a thing, better be prepared to thoroughly understand and review each corner you touch. Or you might miss important cross-references that you should update but that aren't mentioned in comments by the original developers.
As for the "sign in automatically" BS that both Google and Edge push - that can go and die in a hellfire where it belongs.
Comment by sharpshadow 7 hours ago
Comment by Vaushite 4 hours ago
Comment by breakingcups 8 hours ago
Comment by berofeev 8 hours ago
Comment by 1vuio0pswjnm7 2 hours ago
But what hapens when there's no Javascript interpreter, i.e., not the so-called "modern" browser
And when the OS is not Windows
The so-called "modern" browser _is_ a "logic bug". It's multiple layers of stupidity if "security" is a goal
Comment by 1vuio0pswjnm7 26 minutes ago
Comment by cyclopeanutopia 8 hours ago
> I won’t go into too much detail in this post, because I think in this era, you can just ask your agents to fill in the details :)
Comment by russelg 7 hours ago
If you then continued on to read the remainder of the article, you would also discover that there was no AI assistance in this research at all.
Comment by cush 56 minutes ago
Comment by est 8 hours ago
Comment by ncruces 7 hours ago
In fact, a problem with LLMs is that they consistently write more than I want to read.
Comment by maeln 8 hours ago
Comment by MonkeyClub 8 hours ago
Comment by russelg 7 hours ago
Comment by MonkeyClub 7 hours ago
Comment by john_strinlai 2 hours ago
"Anyway, this is what I built for Pwn2Own Berlin 2026 — a completely handmade, logic-only Microsoft Edge Full Chain, with no memory corruption, and no AI at all!"
Comment by tsujamin 8 hours ago
Comment by cyclopeanutopia 7 hours ago