The React2Shell Story

lachlan.nz
162 points mufeedvhabout 20 hours ago 13 comments
AI-Powered Research Assistant
Analyze the comments and suggest other relevant articles to read.

Comments

NewLogic|15 minutes ago
I'm still yet to be convinced React Server Components are anything but a disaster to the developer experience. Mixing backend and frontend without a clear boundary is terrible for any codebase beyond a handful of contributors.
Rauchg|about 11 hours ago
R2S was a painful one, but Lachlan was a dream of a security researcher to partner with. Not just from a responsible disclosure POV, but things like hopping on multiple calls with Meta and our team to help us validate remediations. Thank you Lachlan for helping make the internet safer (and great job on figuring out this 'labyrinth' of a vulnerability)
owebmaster|about 2 hours ago
You ruined React.

But it was quite profitable for you.

halflife|about 2 hours ago
React was ruined from the moment they abandoned class components and introduced hooks. Vercel is just continuing the trend of hype against common sense.
ervine|29 minutes ago
I just don't understand this take, every time I hear it I wonder if people just haven't spent the time to adjust their mental model.

Hooks are IMO the best thing that happened to react.

ascorbic|about 3 hours ago
A great read. Sylvie's writeup is good too: https://sylvie.fyi/posts/react2shell/
sam1r|about 11 hours ago
>> Amazingly, despite being a weekend, the Meta team triaged, reproduced, and confirmed my submission in around 17 hours.

Incredible. Realize what you have done from start to finish (with confirmation) in < 24 hours.

keyle|about 12 hours ago
Nice read!

I love the "we are so back" vs. "it's so over" graph. Defines so much of this type of work. "Wow? ... nah... WOW?! ... nah..."

mnahkies|about 5 hours ago
I was really surprised when this hit, and I discovered the protocol was essentially undocumented / unspecified. I was trying to find indicators of compromise and that was made more difficult by the lack of documentation.

It was really helpful that they had coordinated with WAF providers like cloud flare ahead of disclosure to put rules in place though.

halflife|about 5 hours ago
Whoda thunkit that

- blurring the lines between client code and server code

- creating a brand new protocol for communication between trusted and untrusted actors

- and with all of that allow the protocol to serialize code and not just primitives

Would be a tremendously stupid idea. And for what? To lock developers further into the react ecosystem. What a shitshow react continues to be.

simonreiff|about 11 hours ago
What a great write-up. Thanks for sharing how you found this fascinating vulnerability and exploit.
phyzome|about 10 hours ago
Haha, nice.

One correction: The link in "To be honest, I'm not even sure if I understand it, but it's on my GitHub." goes to the wrong file (01 instead of 00).

mexicocitinluez|about 1 hour ago
Side note: A few weeks ago I started to see floaters in my eyes and the background for your site is making my brain go haywire. Also a tad bit distracting while trying to read the article.

Really cool article btw.