Node.js has just released fixes for 10 security vulnerabilities that could put node-powered applications at risk and is urging everyone to update their systems.
I run a la. Not even a full lamp. Its just a slack box with base apache html.
For years i’ve been mocked. But that bitch has never been compromised and it’s damned near impossible. Who’s laughing now.
What does it do? Serve pictures of cats?
mostly your mum
Static site suprimacy week.
JavaScript should never have been used that way to begin with.
JavaScript should never have been used
that wayto begin with.
How many apocalyptic security flaws can fit into a week?
I never noticed how long the sales guy’s hand is
Why are people mad? These issues existed and now they don’t. It’s not like the researchers created them
“If you don’t test for them, the numbers will go down” - President Trump on COVID-19.
The sky is falling… Except it isn’t. Standard nonsense self advertising. And yes, vulnerabilities exist and canleasd to badness. We agree. It has always been so.
This what you get for running JS as your back end!
This always struck me as a rather silly idea, to be honest.
Now we’ve come full circle. I have a vendor who is insisting that I use node.js and pull their code from their NPM repository from the same… For frontend code. Just, have the entire contents of your (their) node_modules folder exposed to the public internet at all times. Isn’t this just Javascript with extra steps?
While the world reels from websites being taken down before critical PHP patches were released
Is it just me or did anyone else not even notice outside of articles lol… It was all resolved by the time I got off work.
It’s not resolved until everyone installs the patch. And there in lies the problem.
An important point yes and I do understand that, but the major players like Steam were updated and done before I knew it. I have no doubt this could come back to bite companies/people lagging behind over the next few years, but the impact to me from websites being taken down was 0, which was my point.
The companies with well-resourced dev teams would have been able to deal with it. But for every one of those there’s 50 companies with no dev team who are sending frantic emails to the guy who quit 3 years ago asking if he’s available for some urgent work. And another 50 that are not sending any emails because they’re oblivious and will get pwned in a few months.
A lot of PHP apps are old, unmaintained or run by people with no idea. That’s kinda it’s niche.
Yeah but this wasn’t an exploit in PHP applications, this was an exploit in PHP.
Our resolution was to unzip a new directory and change the path to PHP in Apache conf
Yeah, so here’s the thing. People keep trying to bash on PHP as if anything software isn’t manmade and comes baked with flaws that can be exploited. It’s the single reason why cybersecurity products are never going to stop being used because no matter what, it’s based on something somebody made.
It’s going to be flawed or be exploitable by some means. Yesterday it was Log4J, now it’s PHP, tomorrow it will be something else. It will never end. Companies deliberately also use this to force you to upgrade because they’ve abandoned “legacy” products that still work but which they no longer choose to maintain because they want more money and need to stifle you for it somehow.
rihht? opencloud posted a really tacky “nextcloud is dealing with this. checkout open cloud. written in go.”
dude… do we need to drop a link to the golang cves? they had a critical bug this year.
ruby? critical regex rce this week.
nodejs? same.
php made the news because of the embargo break making it go viral and everyone loving to hate on php. But people in glass houses should be careful throwing stones.
How’s Rust holding these days I wonder? Always wished I had learned it when it first came out ha.
apparently i was wrong… https://github.com/rust-lang/rust/issues/164250
haven’t watched it yet but apparently this is a good explanation https://www.youtube.com/watch?v=4iAi5exNHv8
every time the sun rises, shines and sets; a million new node vulnerabilities are discovered
be careful, obviously, but don’t let it turn your entire nervous system into pure crystallized cortisol
you can deal with it on Monday
Has pure HTML (no css, no javascript) ever had a serious security issue? On the server side obviously not (outside of the apache/nginx/etc. having application bugs), but even on the client side has there ever been an exploit?
Nothing wrong with static sites!
I mean I’ll update my Node version, but until someone actually finds an exploit chain on a real system (instead of a vibecoded PoC) I don’t see any reason to panic. All these "could"s and "would"s in the article suggest that it’s kind of a nothing-burger imo
I’ll bet this is another “AI found a known vulnerability so people are making a big deal about it” like the PHP one.
If it’s really a PoC, it would actually execute and therefore exploit something (otherwise it wouldn’t be a proof). In which case it doesn’t matter if it’s vibecoded or not. If you succeed in breaching a system with it, there’s an issue that needs to be fixed.
Yup. Once the PoC has been documented, you gotta patch. Now if you want them to stop vibe coding to find complex PoCs that a human may have never found, it’s a risk.
