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.

top 50 comments

sorted by: hot top controversial new old
[–] 142 points 6 days ago (14 children)
  • [–] 66 points 6 days ago (4 children)

    Nothing wrong with static sites!

  • source
  • parent
  • hideshow 4 child comments
  • [–] 16 points 6 days ago (6 children)

    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?

  • source
  • parent
  • hideshow 6 child comments
  • [–] 9 points 6 days ago

    I think there's been one or two image decompression exploits over the years, so a site with a malicious file could end up running code on your system. I remember this being an issue with Minecraft clients and player skins at one point, but I can't remember any specific times this happened in browsers tho.

  • source
  • parent
  • load more comments (5 replies)
  • [–] 98 points 6 days ago (4 children)

    How many apocalyptic security flaws can fit into a week?

  • source
  • hideshow 4 child comments
  • [–] 21 points 5 days ago (1 child)

    JavaScript should never have been used that way to begin with.

  • source
  • hideshow 1 child comment
  • [–] 29 points 6 days ago (1 child)

    Why are people mad? These issues existed and now they don't. It's not like the researchers created them

  • source
  • hideshow 1 child comment
  • [–] 55 points 6 days ago (10 children)

    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

  • source
  • hideshow 10 child comments
  • [–] 7 points 6 days ago (4 children)

    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.

  • source
  • parent
  • hideshow 4 child comments
  • load more comments (3 replies)
  • load more comments (2 replies)
    [–] 11 points 5 days ago

    Static site suprimacy week.

  • source
  • [–] 22 points 6 days ago (7 children)

    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.

  • source
  • hideshow 7 child comments
  • [–] 20 points 6 days ago (4 children)

    It’s not resolved until everyone installs the patch. And there in lies the problem.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 5 points 6 days ago* (3 children)

    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.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 9 points 6 days ago (2 children)

    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.

  • source
  • parent
  • hideshow 2 child comments
  • load more comments (1 reply)
  • load more comments (2 replies)
    [–] 34 points 6 days ago (2 children)

    This what you get for running JS as your back end!

  • source
  • hideshow 2 child comments
  • [–] 23 points 6 days ago

    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?

  • source
  • parent
  • While it's a bit opportunistic to blame JS in the backend in this case, I despise JS in the backend enough to happily join you.

    Serves you well JS enthusiasts, your programming language is the only one that I despise more the more I learn about it. :P

  • source
  • parent
  • [–] 30 points 6 days ago (2 children)

    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

  • source
  • hideshow 2 child comments
  • load more comments (2 replies)
    [–] 18 points 6 days ago (3 children)

    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.

  • source
  • hideshow 3 child comments
  • [–] 8 points 6 days ago (2 children)

    Well, I mean, the AI advances have moved the mean time to exploit between a zero day being announced, and it actively being exploited en masse, from about 3 weeks in 2018, to about -1 day in 2026. So, things have changed a bit.

  • source
  • parent
  • hideshow 2 child comments
  • load more comments (1 reply)
  • [–] 20 points 6 days ago (6 children)

    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.

  • source
  • hideshow 6 child comments
  • [–] 8 points 6 days ago (4 children)

    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.

  • source
  • parent
  • hideshow 4 child comments
  • load more comments (4 replies)
  • load more comments (1 reply)
    [–] 3 points 4 days ago (2 children)

    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.

  • source
  • hideshow 2 child comments
  • [–] 15 points 6 days ago (5 children)

    Imagine working in IT security. How bad a time are you having right now? Are we expecting things to become better or worse the next few months?

  • source
  • hideshow 5 child comments
  • load more comments (4 replies)
    [–] 5 points 5 days ago

    Node has literally always been like this. It’s just a risk you accept when you choose to use it.

  • source
  • load more comments
    view more: next ›