Programming

23835 readers

119 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

UlrikHD@programming.dev

106

React2Shell: maximum severity vulnerability discovered in React (www.tenable.com)

submitted 4 days ago by ExLisper@lemmy.curiana.net to c/programming@programming.dev

8 comments fedilink hide all child comments

I got an email from Vercel urging to upgrade Next.js based project 3 days ago. POC was published 2 days ago. Today I've checked my logs and I could already see attack attempts.

you are viewing a single comment's thread
view the rest of the comments

[–] portnull@lemmy.dbzer0.com 8 points 4 days ago (1 children)

Are we still vulnerable if our app doesn’t use React Server Functions endpoints?

Potentially. According to the React Team, even if React Server Functions are not in-use, the vulnerability is still exploitable if React Server Components are supported.

[–] TehPers@beehaw.org 6 points 4 days ago (1 children)

I think their point was that CSR-only sites would be unaffected, which should be true. Exploiting it on a static site, for example, couldn't be RCE because the untrusted code is only being executed on the client side (and therefore is not remote).

Now, most people use, or at least are recommended to use, SSR/RSC these days. Many frameworks make SSR enabled by default. But using raw React with no Next.js, react-router, etc. to create a client-side only site does likely protect you from this vulnerability.

[–] kungen@feddit.nu 4 points 4 days ago (1 children)

Now, most people use, or at least are recommended to use, SSR/RSC these days.

Why though?

[–] TehPers@beehaw.org 2 points 3 days ago

I'm not the one recommending it lol.

If I had to guess, it's to improve page performance by prerendering as much as possible, but I find it overkill and prefer to just prerender as much of the page as I can at build time and do CSR for the rest, though this doesn't work if you have dynamic routes or some kind of server-side logic (good for blogs and such though).