Programming

24097 readers

265 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

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

submitted 3 weeks ago by ExLisper@lemmy.curiana.net to c/programming@programming.dev

7 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

[–] Mikina@programming.dev 7 points 3 weeks ago* (last edited 3 weeks ago) (1 children)

Well, Element seems to still be running at the unupdated version even after update, so I'm just shutting the server down.

I'm bummed that it took me 5 days to learn about it, does anyone have some tips how to get early warnings for techs you're using? I'm guessing there's a way with npm.

Also, anyone has some tips how to properly compromise-check your server? I'm guessing there are logs to check for compromise, and audit your startup scripts for persistence? Any tools that could help with that?

[–] GammaGames@beehaw.org 3 points 3 weeks ago* (last edited 3 weeks ago)

Renovate can flag CVEs in its pull requests, if you just want to check versions