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.

  • TehPers@beehaw.org
    link
    fedilink
    English
    arrow-up
    4
    ·
    22 hours ago

    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
      link
      fedilink
      arrow-up
      3
      ·
      20 hours ago

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

      Why though?

      • TehPers@beehaw.org
        link
        fedilink
        English
        arrow-up
        1
        ·
        11 hours 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).