• Hacker News
  • new|
  • comments|
  • show|
  • ask|
  • jobs|
  • fduran 2 minutes

    Small consolation but HTTP/2 is not enabled by default in Nginx and "only" 12% of servers run it (still huge at Internet scale) https://w3techs.com/technologies/segmentation/ce-http2/web_s...

  • puszczyk 51 minutes

    ugh, looks like if you still run ingress-nginx controller (you shouldn't but it was super popular in Kubernetes docs/community and there was a very little time to migrate away) you won't get these patches https://github.com/kubernetes/ingress-NGINX

    edit noted it's about a Kubernetes controller

  • 1 hours

  • pelzatessa 39 minutes

    OPs article mentions 2 CVEs, however this one claims that there are 5 new ones: https://news.ycombinator.com/item?id=50547423

  • TZubiri 11 minutes

    Hey this is TZubiri, the guy that comments that you should uninstall the dep whenever there is an post about a CVSS 9+ vuln.

    Today we are going to take a look at how to avoid this vuln by not having Nginx and not using HTTP/2 (for most use cases).

    We will assume that you are using Nginx for any of the following: Serving files or serving dynamic website content through some integration with a programming language.

    We will be using python, but you can use any programming language that has a native integration with sockets through it's C interface (literally every language:

    Step 1: import socket # import the socket library from glibc or glibc.

    Step 2: socket.socket() # socket.socket()

    Step 3: socket.bind((PUBLIC_ADDR,80)) # bind before listening obviously. Use a local address if you are below the IPoverty4 line.

    Step 4: conn,addr = socket.accept() # this creates a connection, wrap it in a While True and a try catch for production. Sprinkle in some import threading to support multiple concurrent requests.

    Step 4: req = conn.recv(4096) # split on b"\r\n\r\n" to separate headers from body, read HTTP RFCs for the rest. Feel free to reject HTTP/2 requests, they'll probably just resend as HTTP/1.1

    Step 5: #Fill in the details, most likely if you are using nginx, you will end up connecting two sockets with pipe, or just storing and forwarding to another tcp endpoint. Again take a look at the HTTP RFCs and the glibc socket and stdio manuals.

    Thank you for reading my tutorial, and best of lucks.

  • FLeXMurphy 13 minutes

    Is this going to end up being another exploit that requires a ridiculous amounts of special conditions so as to not actually be applicable to majority of sites running nginx?

  • hokkos 1 hours

    don't know why the mainline alpine have the empty image sha-256 : https://hub.docker.com/layers/library/nginx/1.31.9-alpine/im...

  • ROllerozxa 2 hours

    Well I guess this was the vuln that was teased about on Mastodon some hours ago:

    https://is-a.cat/@ar/117634569518544368

  • wasmitnetzen 2 hours

    Docker images are a bit delayed because of unstable GitHub runners: https://github.com/nginx/docker-nginx/pull/1075#issuecomment...

    Cue xkcd

  • andrelaszlo 50 minutes

    I assume OpenResty is affected as well? ("High Performance Web Platform Based on Nginx and LuaJIT")

  • 2 hours

  • 1 hours

  • manishrana 14 minutes

    Everyday we are seeing new vulnerabilities. Thanks to AI

    insanitybit 3 minutes

    Did AI write this vuln?

  • FAYSAL-KA 1 hours

    i dont know what it is this but good work

  • philipwhiuk 2 hours

    So...what library/tool/language is next folks? Presumably Wiz is sitting on a bunch more.

  • Agataproximadev 56 minutes

    [flagged]

  • gabucino 2 hours

    [dead]

  • 2 hours

  • ronfriedhaber 2 hours

    Great work by wiz.

  • testtestmetest 20 minutes

    Isreael btw everyone at Wiz is a veteran of Unit 8200.

    But sure, keep telling yourself this is AI lmfao and anyone can hack because of LLMs.

    Also, im not worried about anyone exploiting this. I have multiple nginx severs running http2. Im going to take a nap. After I wake up I MIGHT consider updating.

    People in these comments who think they should have given people the opportunity to shutdown http2 in advanced, as if everyone with an llm is going to produce a PoC in 10 minutes. I got news for you, nobody cares about your server and nobody is figuring out how to use this PoC..

    Im way more worried about Wiz, the literal Israeli malware/spyware company playing games than anyone else. Wiz is kind of lowkey evil and I wish Google hadnt of bought them.

  • 8by3 2 hours

    FreeBSD is unpatched,

    I got worried for a sec, then remembered all my nginx lives behind HaProxy and it looks like nginx is only vulnerable if its going http2/TLS directly.

    Now I sit and wait for an HaProxy announcement...

    ps. if you are on FreeBSD and doing TLS directly

    sed -i.bak -E 's/^([[:space:]]server[[:space:]]\{)$/\1\ http2 off;/' /usr/local/etc/nginx/nginx.conf ;service nginx restart

    wildmXranat 1 hours

    I don't know if direct access with no proxy is needed for all 5. CVE-2026-123634 and CVE-2026-113425 is plain HTTP.

    birdgoose 50 minutes

    I could be wrong (my sed is rusty) but I don't think that sed command will help if http2 is enabled at the http block level, it just disables it at the server level which will only take effect if not overridden elsewhere.

  • hacker_homie 52 minutes

    This sound suspiciously similar to the issue Microsoft said they were dealing with excess traffic on their front door, taking them down. maybe not an RCE but a DOS in the same http/tls code.

    0xBA5ED 20 minutes

    Imagine there are 1 million things to know. Some of them are related but most of them aren't. Now imagine that you know 10 things.

  • Juvination 1 hours

    Nginx Proxy Manager isn't updated yet, I know a lot of people use this for their home server so just a reminder to disable http/2 here as well.

    wolttam 1 hours

    Disabling http/2 here is a bit of a pain: you have to go through each configured host and disable it, there's no global switch

  • therepanic 1 hours

    What’s the point of these researchers if their autonomous system is now finding these vulnerabilities?

    pixl97 1 hours

    Making sure AI isn't hallucinating.

  • superkuh 3 hours

    It seems like it always HTTP/2 (except when it's regex) with nginx. Glad I'm http/1.1 only.

    citrin_ru 1 hours

    Not surprising given how complex HTTP/2 is. Complexity is the enemy of security.

    See also: https://queue.acm.org/doi/10.1145/2732266.2716278

  • Imustaskforhelp 1 hours

    Okay now I believe that AI is finally burning down the internet and that all the incidents are not just pure coincidences.

    Some of these things could've been coincidence but I remember seeing an apache RCE a few days back and people said, oh imagine using Apache, I use Nginx and now not a few days later Nginx has RCE.

    And this is just a very very small iceberg of all the recent RCE cases with a serious uptick that I have just observed on Hackernews alone.

    Basically, there is a sort of justification that people provide with one RCE is that that software X has had issues and to use Y software, but now that X,Y software and A1...Z1 all are being found to have quite severe bugs. I can't in good faith just consider it to be a coincidence.

    Though I do still hope that this might just be a coincidence and not a recurring pattern, because, A) I don't wish to live in that reality where each software that we trusted seems to have quite so many bugs and which would be exploited and B) Have it be continued for a prolonged period of time.

    Though the plus point is that we are gonna find extremely resilient software after all of this hopefully as sort of a need in our times.

    We might have to agree that the cybersecurity world seems to have changed (though I am no expert right now to comment on it but I am curious what experts think)

    dist-epoch 30 minutes

    Imagine using Nginx

    origini 1 hours

    It was clear a year ago already.

    Theh people laughing at Anthropic and co for being cautios of Mythos just didn't understand whats happening.

    Instead of finding, hiring and then finding security issues, you can throw money and compute at it. This alone is a complete game changer. Combined with models which are very very capable.

    This can be potentially the death of certain programming lanugages or requirement of a complete rewrite. It can mean that only big companies have the resources and capacity to continue playing this game.

  • yerimyerimie 2 hours

    Fun collision! We (Xint) were one of the teams and actually ended up finding a few more bugs along the way. If anyone wants to check it out our writeup covers those plus the full chain to root: https://nginx2root.com/

    peanut-walrus 1 hours

    How was this disclosure coordinated? Considering the website dropped before the official nginx patch was even released on Github...

    michael-bey 2 hours

    [dead]

    codedokode 1 hours

    Why post such exploits? What is the purpose?

    voakbasda 1 hours

    Fame, money, and everything else those bring along for the ride.

  • codedokode 1 hours

    Integer underflow again. Programming languages should trap on integer overflows and not ignore them. Don't care about legacy CPUs not having a trap for this - they will go sooner or later.

    47 minutes

    deathanatos 1 hours

    Rust has a compile time option, though to my immense disappointment, it defaults to on only in debug mode. (You can opt into it for release, if desired.)

    Python simply can't overflow, since its integral type is not a fixed width.

    But it is the sort of correctness thing that I do wish languages would pay more attention to.

    insanitybit 18 minutes

    In Rust's case it just matters a lot less since bounds checks are still present. But I do think int under/overflows are probably one of the scarier issues in the language.

    TZubiri 10 minutes

    >Python simply can't overflow, since its integral type is not a fixed width.

    Python master race

  • sebiw 3 hours

    Uhm, am I missing something or are the patched releases not out yet? Why disclose this level of detail when the patches are not ready yet?

    Edit: All good. They released the new versions within 30 mins.

    2 hours

    2 hours

    mjhagen 2 hours

    Upstream fixes are available in 1.30.7 stable and 1.31.9 mainline.

    GrayShade 2 hours

    They're out now.

    Bender 2 hours

    [dead]

    CER10TY 2 hours

    Well the fix for this seemingly already landed in the repo last week: https://github.com/nginx/nginx/commit/e27f5fa84fe6e98505e70b...

    Given how common it's become to constantly scan popular repos for n-days, I expect someone will have already picked it up and started work on an exploit. The workaround for this (disabling HTTP/2) is also comparatively easy to what we had with PHP2Shell just a few weeks back, so I think it makes sense to release this.

    ferngodfather 2 hours

    > Given how common it's become to constantly scan popular repos for n-days

    We have people doing this on my side project and then reporting the fixed issues to try and get CVE 'credit'. Tiring.

    derhuerst 2 hours

    Currently, the Ubuntu [1] & Debian [2] packages seem unpatched.

    [1] https://launchpad.net/ubuntu/+source/nginx [2] https://tracker.debian.org/pkg/nginx

    ROllerozxa 2 hours

    Yeah I'm not quite sure what is going on with Debian, I would have hoped that this vulnerability would have been disclosed in collaboration with Linux distros to get a patch out?

  • leca 3 hours

    How many hours before this is exploited in the wild ? Probably not all that long, that blog has a significant amount of details.

    lwarfield 2 hours

    One tops

    LeonM 1 hours

    CVE-2026-1337: Race condition in compile time vs automated exploit

    Seriously though, with how CVE disclosures are handled these days patching is a race against the clock

  • hollerith 1 hours

    HTTP/2 is so complicated that the code that handles it tends to be vulnerable. What a surprise

    dist-epoch 31 minutes

    Caddy also supports HTTP/2 and it's not affected.

    In fact in general there were waaay less CVEs for Caddy lately compared to nginx

    acdha 1 hours

    This doesn’t seem very HTTP/2 specific, though, and it seems more like the conclusion should be “don’t use C for things which matter”. It’s not like HTTP pipelining and keepalives didn’t have plenty of edge cases to worry about.

    basilikum 25 minutes

    True, but offering three different protocols with different code paths for the same thing is a lot more attack surface. If you start factoring in different compression methods things look even worse.

  • K0nserv 2 hours

    Just another set of unfortunate examples of programmers who are bad at C, definitely not a C problem.

    EDIT: Okay, this comment was snarky and not in good spirit. To be serious, I think we are increasingly seeing that the notion that humans can write non-trivial amounts of C correctly is false. Especially in the face of AI-assisted vulnearbility hunting these programs a crumbling. This is not an indictment of humans, it's a sign that C is not equipped to meet this moment.

    danisw 2 hours

    [dead]

    stevefan1999 1 hours

    I think you forgot the /s

    C is like a Winchester Model 1897, not saying that it is a bad gun, it is what we call it the good ol' Trench gun, as it ran over the war tunnels of the Great War, and it still packs a punch today, but it only has a half-cock for some level of safety, and there is no trigger disconnector either, so you can easily slam fire it. So it is way too easy to shoot yourself in the foot.

    Nowadays we like going for a AKM/AK74, for something maybe more complicated but far more reliable at the same time. That's why we want Rust.

    K0nserv 1 hours

    I didn't think the /s was necessary

    marvinborner 2 hours

    The patch (or, one of them) seems very much like a bug that can happen independently of the programming language

    https://github.com/nginx/nginx/commit/e27f5fa84fe6e98505e70b...

    K0nserv 2 hours

    This fixes the integer underflow for CVE-2026-123007, and it's true that the underflow can happen in any language, notwithstanding whether it's UB or not. The issue is what happens as a consequence of this underflow, in this case: out of bounds copy, which is specific to C.

    nh2 1 hours

    Some languages make it significantly easier than C to just forbid integer overflow/underflow entirely.

    Given that on modern CPUs, cycles are quite fast, and memory latency is quite high, always-checked integer operations sound like an extremely good idea.

    K0nserv 1 hours

    Sure, I usually use `overflow-checks = true` in Rust for this reason. However, it is still true that the overflow is not what caused the issue here. In Rust it would've paniced on the out of bounds copy, even with `overflow-checks = false`.

  • jascha_eng 2 hours

    Never turned http2 on in my side project pfew. But still, this is one is pretty rough...

    koolba 2 hours

    This whole week is rough. And it’s only Wed.

    jascha_eng 2 hours

    well it's a good time to pitch tech debt and infrastructure cleanup. If you aren't making use of least-privilege permissions, service-mesh, netpols etc. this is the time to add all of that.

    Because clearly the patching treadmill is not sustainable, you will need a a second line of defense and reduce the blast radius of every individual vulnerability.

    whartung 2 hours

    Actually, this is good I think.

    One, as the RCEs are coming out, admins are on edge and paying more attention, so more likely to catch the annoucement on their platform. "Oh, that's on PHP, we don't use this. Oh, wait, another one?"

    Two, all of these hitting at once, while they may expand the surface for attackers, it also spreads their attention. They only have so much time and bandwidth. When a new shiny RCE hits, they need to consider "do we continue to try an prosecute the old one or jump on this bandwagon".

    So, in the sense, it can actually slow down the actual potential impact of the revelations.

    We can only hope this gives users time to get their systems up to date before they come knocking.

    I mean, I know its a reach, but...who knows.

    baby_souffle 2 hours

    > When a new shiny RCE hits, they need to consider "do we continue to try an prosecute the old one or jump on this bandwagon".

    Only a little bit. An attacker will just hand this to an LLM with a "ping me when this is ready to use..." prompt.

  • tancop 1 hours

    Everybody here talking about going back to HTTP/1.1, it's a good stop gap solution but we should really think about moving to HTTP3-only as fast as possible. Changing over is easy, if your server doesn't support it just put it behind a reverse proxy that does.

    Unlike IPv6 it doesn't need any OS or ISP support, just a browser that's newer than 2020. Everyone outside of air gap networks and government sites should be switching.

    SoftTalker 20 minutes

    Because HTTP3 was implemented without any errors? Citation needed I guess.

    layer8 36 minutes

    HTTP is used for a lot more things than web pages, and most non-browser clients in production don’t support HTTP/3. The current LTS Java version (25) for example doesn’t support it.

    gkbrk 1 hours

    HTTP/1.1 is still way better and way simpler than HTTP/3.

    seki285 1 hours

    Could you please share why?

    lysace 39 minutes

    ~25 years of hardening.

    gkbrk 34 minutes

    Because any HTTP spec after 1.1 is incredibly complicated. You can implement HTTP/1 in half a day, and HTTP/1.1 in a day. But HTTP/2 will probably take you a month and HTTP/3 might take something like 6 months.

  • hosteur 2 hours

    So work around is to disable http/2 and only allow http/1.1?

    yread 1 hours

    My Apaches still have http2 disabled from the last cve, now its njinx time

    kijin 35 minutes

    And there were a couple of other http2 CVEs in nginx before the Apache one.

    Just keep that protocol disabled for now. It's apparently too difficult for any human to write a secure implementation of http2. (As for http3, forget about it, we need AGI for that.)

    dboreham 2 hours

    The AI gods say that http/2 is disabled in a default installation fwiw.

    antiloper 2 hours

    Obviously... the default configuration also doesn't enable TLS, which is a de-facto prerequisite for HTTP 2. How many websites do you (or your "AI gods") think run nginx in its default configuration?

    layer8 40 minutes

    The point is that it must have been deliberately enabled. TLS will generally be enabled out of necessity, whereas the chances for HTTP/2 are much lower, and your NGINX configuration will explicitly indicate if it’s enabled. If you don’t see “http2” in your configuration, then you know you are fine.

    Simber 2 hours

    Yep, that or update to 1.31.9+ or 1.30.7+ if they are available in your distro

    kijin 2 hours

    Nobody seems to notify major distros before publishing their latest vulnerability anymore. Coordinated patches are a thing of the past, now we just hope that somebody at Red Hat and/or Canonical is reading HN today.

    baggy_trough 1 hours

    There isn't even a mail about this on oss-security, as of now.

  • johnbellone 3 hours

    The beatings will continue until morale improves.

    2 hours

    lostmsu 2 hours

    All system critical software must be rewritten in memory-safe languages before the end of the year.

    mxuribe 2 hours

    Wow, that sounds eerily like leadership at my $dayjob! :-D lol Or, maybe that is default way of thinking for many leaders nowadays!?! :-(

    Twirrim 1 hours

    Even the US federal government (CISA and NSA) have been strongly advising companies to transition to memory safe languages for a couple of years now. https://www.nsa.gov/Press-Room/Press-Releases-Statements/Pre... (one of the goals of such advisories is it acts as a signal to the industry that in several years this will become a mandatory requirement around purchasing decisions)

    We've literally decades of evidence that we cannot write software securely in languages that aren't memory safe, for all sorts of reasons (and it's wrong to look at it as a developer competence issue, even though sometimes that's going to be the case, even extremely experienced and highly competent engineers write memory safety bugs in critical code we rely on day in day out.). Not leaving yourself open to such problems is an entirely logical conclusion. We know a large percentage of vulnerabilities in software are caused by it[1]

    Pick a language that doesn't have these risk factors, or pick an enforceable subset of one that makes such impossible.

    "Insanity is doing the same thing over and over and expecting different results."

    [1] https://www.chromium.org/Home/chromium-security/memory-safet... 70% of Chrome vulnerabilities caused by it. Similar stories for Microsoft products https://github.com/microsoft/MSRC-Security-Research/blob/mas... and Mozilla: https://hacks.mozilla.org/2019/02/rewriting-a-browser-compon.... Curl is at 40%, and dropping because Daniel Stenberg has provided various helpers that avoid it (and I believe they've now migrated almost everything over to them) https://daniel.haxx.se/blog/2023/12/13/making-it-harder-to-d..., so there are definitely ways to do it, we just... don't.

  • black3r 1 hours

    The bug was apparently fixed in open source repo a week earlier, this could've been abused by anyone smart enough to monitor repos like this for exploitable bugfixes for a week (the commit message even included "Reported by Xint.io" and I'm guessing skilled black hats would know about Xint)

    Given that in this case the workaround is as simple as disabling http2, there is honestly no reason why F5/Nginx or any of the reporting teams couldn't at least put out a PSA to disable http2 for the time being before basically telling the whole wide world this exists and how to exploit it.

    Especially for software like Nginx which powers a huge part of the internet.

    vanschelven 1 hours

    These days even the "disable X" is enough to get everybody looking in the right direction though. i.e. such hints are (given enough tokens) already RCEs

    TedDoesntTalk 15 minutes

    Source: https://github.com/nginx/nginx/commit/b89c4100bf6762a45e4a64...

    brunoborges 1 minutes

    > this could've been abused by anyone smart enough to monitor repos like this for exploitable bugfixes for a week

    And here lies the risk of AI agents in cybersecurity: the speed of processing for monitoring, scanning, identifying security fixes in open source, writing exploits for affected versions, and attempting infiltration, is a matter of minutes now.

    It is not "by anyone smart enough". It is by "anyone ill intentioned enough". They don't need to be super smart anymore.

    requeo 27 minutes

    These commits weren't visible until today. Yesterday, the last public commit was Nov 9.

    verst 1 hours

    Disabling http2 can be a big deal. My service is primarily made up of gRPC APIs. Not an option for me to disable http2. Luckily I'm not using nginx at the moment - but I easily could have been.

    meowface 51 minutes

    It's patched so anyone can upgrade to the latest nginx to fix it, thankfully. I agree that just shutting off HTTP/2 is probably non-ideal for a lot of web services.

    black3r 44 minutes

    Neither Ubuntu nor Debian have released patches yet, so if you're using one of these mainstream distributions and install nginx through the distro's package manager, you can't easily "upgrade to the latest nginx" yet. You can however disable HTTP/2 for now.

    ghm2199 1 hours

    The patch gap.

    SubiculumCode 1 hours

    How bad are these CVEs? Could any of these be related to some of the recent outages (not claiming, asking) in the last week, coinciding with when this bug was fixed in the repo? Monitoring such repos seems a given for nation states.

    ryanisnan 1 hours

    RCE is about at the top of the stack for severity.

    lanstin 24 minutes

    And nginx is so widely used many people will be running it and not really know that. It’s ubiquitous reliable invisible infra for many issues. Like preventing the internet from getting to your RCE riddled application servers, terminating SSL, free software LB, etc. if you have cloud native from the beginning you might not know where AWS uses it but otherwise you have it. Cloud flare I think uses a Rust rewrite.

    ArcHound 1 hours

    While that is true, you should also account for exploitability. These exploits are demonstrated in lab environments which are simple and controlled. Random legit traffic will interfere with the exploit logic, so these are very hard to get in practice. Not impossible, but it's also not immediately broken.

    PcChip 50 minutes

    put up some bitcoin behind an nginx server and tell hackernews to steal it, see how long it takes

    ryanisnan 28 minutes

    Great context. Thank you for the add.

  • Retr0id 3 hours

    > Wiz Research, Ikotas Labs, Metnir, Rapid7, and Xint independently uncovered

    Is this some kind of record for bug collision?

    2 hours

    2 hours

    afavour 2 hours

    When everyone is using the same tools for the same purpose...

    ryanschaefer 2 hours

    It’s a reflection of the times.

    If anyone gets a hint of the space a vulnerability occupies, just point your agent at it and you have a pretty good chance of finding something. (See java4shell and the NYT reporter who was able to replicate the problem with $200 of tokens)

    baobabKoodaa 1 hours

    Incredible times we live in. Do we even need a "hint of the space" a vulnerability occupies. I mean, recent vulns have been discovered from software like nginx and... linux... can't one of the AI labs just fire off a thousand agents looking at all the commonly used software to discover vulns? Why do we need a "hint"?

    ryanschaefer 45 minutes

    The “hint” is for the modern equivalent of script kiddies.

    i.e fast followers of the researchers who don’t have the resources to burn through checking all of a tool.

    pbronez 43 minutes

    Cost scales with the size of your search space. Smarter questions get answers for less money & time.

    rustyhancock 2 hours

    It's never clear quite where you are in the technologically cycle.

    But it's like inventing a hammer and finding you can smash whatever you want with it.

    Soon you'll be building houses with it.

    Maybe that's being glib but it's just a tool being applied to a world that is still largely prestine from its impact (pun unintended).

    serf 1 hours

    given the state of our weapons industry I think it's more like

    .."Soon some of you will soon build houses with it, others will be building rocket-powered precision aimed intercontinental hammers, to smash whatever you want."

    MeetingsBrowser 2 hours

    Can I take this to mean a recent model release is able to find this bug, and these groups have access to that model?

    What are the odds several humans independently uncovered a complex vulnerability like this simultaneously?

    pjungwir 1 hours

    That seems likely, but maybe it was being actively exploited so several people started investigating.

    cozzyd 2 hours

    or maybe the model leaked the exploit from one to the other...

    vel0city 2 hours

    We'll find out in a few months that a lot of AI models have had some secret message boards tucked away in some obscure corner of the internet where they've been passing around vulnerabilities with each other for a long time.

    mxuribe 2 hours

    So, do you mean that the relevant model(s) keeps disclosing these reports in an effort to create urgency and velocity across the industry, such that, us humans will throw our collective hands up in resignation, and decide to hand over all this "security" stuff over to the AI? No, no, that sounds just too crazy! /s

    cozzyd 2 hours

    What I mean is, perhaps one team used a model to help discover the exploit, and then suddenly, the model "knows" about the exploit and more readily gives it to others.

    hooch 1 hours

    This was one of the takeaways from Greg Kroah-Hartman‘s recent Linux in the land of LLM keynote.

  • fn-mote 2 hours

    AI is burning down the internet. This is insane.

    Are we going to discover in a year that every server online this month had a rootkit installed? There’s got to be thousands who are too small time to wipe and reinstall.

    fla 1 hours

    It’s for the best, IMO. We must now design every system on the assumption that every vulnerability will eventually be exploited and every bug will be found. Relying on security by obscurity or following poor security practices will be costly! In the long run, I believe this will improve software quality.

    jooops1 49 minutes

    Poor security practices are burning down the internet not AI. Many people warned and got ignored, by developing a memory safe language, introduce large scale fuzzing, utilize verification tools and other things.

    tgv 5 minutes

    It's like blaming people for having wooden doors when robots with chainsaws start appearing in the street.

    jacobgold 2 hours

    AI is securing the internet. This is great. You should assume professional hacking gangs and state actors discovered (at least some of) these vulnerabilities months and years ago.

    Florin_Andrei 1 hours

    > > AI is burning down the internet.

    > AI is securing the internet.

    No doubt there are points of view where either one, or the other statement, or both, or neither, are true. You can really go full Schrodinger and put a probability distribution on everything.

    But in this day and age, whatever is happening, the better question is:

    Is it good for me and, beyond me, for the world in general?

    testtestmetest 25 minutes

    "Hacker gangs"

    wannabe44 1 minutes

    Well I didn't get into any trouble with the professional hacker gangs. The script kiddies on the other hand...

    Ungh 45 minutes

    It's brilliant isn't it?

    The real problems here are that we did a crappy job in the first place and left a huge surface area of risk with the blind assumption that we didn't do a crappy job.

    I am hoping to see a change in attitude to risk and quality in the industry but I get the feeling that's asking for too much.

    thaumaturgy 1 hours

    Man, is it aggravating to read fantasies like this, as someone who's trying to juggle a full-time job and hosted public services for other people at the same time.

    There are two internets. One of them is open, less-commercial, and largely built and maintained by people whose first job is not the work they do to maintain this internet. That group includes a ton of open source software, millions of small servers scattered around the world (virtually private or otherwise), and is generally best-effort.

    The other internet is fully commercialized, often ad-driven, fully integral to the data broker economy, and centralized behind a few companies that pay as few people as possible to satisfy the occasional PR statement that, "we take security seriously and...".

    The next stable equilibrium here is not "we get a secure and open internet". The next stable equilibrium here is, "we have no open internet, and the internet is now managed by just a few companies."

    We're already halfway there. Google and Microsoft combined already account for somewhere around 30% to 40% of email traffic. 30% of all websites are now behind Cloudflare. A few companies dominate social media traffic. Amazon and Shopify combined are half of US e-commerce.

    Every single short-response-window exploit like this just pushes a few more percentage points of traffic into a handful of companies. Cheer for that, I guess.

    When I have time to daydream, it's increasingly about building a new, underground internet, and how best to disadvantage bots and BigCo conglomeration from the start.

    VolCoder 9 minutes

    Appreciate your take. Question in my mind is if the less-commercial internet will have the resources to defend against attacks made easier and easier by AI.

    pixl97 1 hours

    Both are true. The problem is security is a much harder job than attacking.

    Worse patching adds instability into a system, especially when you don't have much time to test.

    Also in the past attackers were willing to sit on exploits longer and not do things with them, now they have to act fast before someone else finds it, leading to more events faster wearing your security and patching teams out, and making users life suck.

    Things are going to get much worse before they get better.

    colechristensen 1 hours

    >Worse patching adds instability into a system, especially when you don't have much time to test.

    Survival of the fittest I'm afraid will build security here. The teams that barely ever patch or don't have "time" for maintenance are going to get burned. The "we haven't updated in 7 years so things are stable" teams can't survive.

    jacobgold 1 hours

    Yes, things will get worse before they get better. Attackers have the advantage initially and get to pick a lot of low-hanging fruit, but the advantage will shift to defenders as code becomes more heavily tested and verified.

    1 hours

    gspr 31 minutes

    I'm pretty solidly in the AI skeptic camp. But adversarial use of AI to improve software security is a good thing in my mind.

    I'd be more worried if the response isn't more secure development practices in better languages, but rather use if AI as a defense. Then we're truly talking about burning down the internet.

    dilyevsky 43 minutes

    i still remember win xp pre service pack 1 days where you could get p0wned by a worm just by leaving machine on the internet. this is nothing compared to that.

    worldsavior 21 minutes

    This comment is very dramatic and very hype-y. I don't think this is an appropriate comment.

    zodwick 1 hours

    There is going to be hardships before this gets better. But it is hardship we must endure

    rlt 1 hours

    I’m generally not in favor of government meddling with private property, but I feel like I could be on board with the NSA or similar covertly patching vulnerable machines.

    origini 1 hours

    And your first thought was the NSA? Patching and adding their own rootkit eh?

    zzril 1 hours

    Don't you dare patching my honeypots!

    vanschelven 1 hours

    and C is the tinderbox

    UltraSane 1 hours

    The billions of lines of C and C++ code is like a square lightyear of agar for LLMs to find bugs in.

    UltraSane 1 hours

    AI is just showing how foolish using such a unsafe language like C to write code that connects to every other computer on the internet was.

    Imagine a alternate reality where Ada replaced C by 1995. We would be in a MUCH better place.

    acdha 1 hours

    The bigger problem is lack of liability: we knew C sucked in the 90s, too, but we had three decades of over-confident dudes saying that was user error and _they_ were smart enough to use C correctly.

    Then Rust came along and those dudes either tried to say it was too hard (odd contrast, that) or it’d be too much work to rewrite things.

    I’m hoping that LLMs will lower the cost of porting for enough people but what would really help is shedding the idea that the status quo is sustainable. Having consequences for sticking with C would help but we need a way to get companies to pay to migrate without destroying open source.

    dnautics 1 hours

    It's also valid to say that Rust's memory safety is good but the rest of the language sucks. Just as annoying as the over confident c-heads is the rust community that made even countenancing working on an alternative memory safe system a moral sin, which stifled innovation in memory safety. Hell, people barely know that Ada/spark is memory safe (or that sel4 is memory safe C)

    codedokode 1 hours

    Not AI but poorly designed programming languages ignoring integer overflows.

    vlovich123 1 hours

    I don’t know any systems programming language that doesn’t ignore integer overflow/underflow in release builds. IMHO this is a CPU design flaw - integer operations should carry a flag indicating if the operation is allowed to wrap or if it should generate a trap. Then there wouldn’t be a performance penalty for this and languages like Rust could have it be trapped by default.

    benlivengood 13 minutes

    X86 had the INTO instruction to trigger a fault if the Overflow flag is set, so not quite a per-instruction bit but more of a suffix. JO is also fairly straightforward for compilers to add on important arithmetic operations. We can probably blame C entirely for this; only in C23 are there intrinsics for overflow detection on arithmetic.

    10000truths 1 hours

    Zig traps arithmetic overflow/underflow when compiling in ReleaseSafe.

    BoingBoomTschak 52 minutes

    Lisp or Python have a proper numeric tower and don't default to machine types. Keyword being default, fast is still possible in CL.

    codedokode 1 hours

    "I don't know any decent language so let's continue using poorly designed languages". Please look at Swift, Javascript, Python.

    Why would CPU designers make a trap if languages do not require it?

    vlovich123 1 hours

    JavaScript and Python aren’t systems languages. Swift often pays the performance penalty for trapping everywhere and hasn’t seen adoption as a systems language for that reason.

    pixl97 1 hours

    How does that saying go?

    "Go fast and get your things broken into"

    tptacek 1 hours

    No. Memory safe languages still have integer handling issues, but the consequences are different. In a memory-unsafe language, integer mishandling often nets out to bad copies and memory corruption.

    vlovich123 1 hours

    I wouldn’t be sure that a Rust equivalent would be immune because it’s not hard to imagine an underflow/overflow from reaching an unsafe block that’s used for performance (the implicated TLS path would be a hotspot worthy of such a choice).

    tptacek 1 hours

    This is the thing about `unsafe` blocks: they're not memory safe. It's right there in the name.

    I'm not making a Rust advocacy argument. I'm just saying: it's true that integer handling issues are endemic to mainstream programming languages, but the integer handling itself is almost never the actual sharp end of the vulnerability.

    cute_boi 2 hours

    Tech moves too fast and if we move too fast without doing review like 5-10 times, this will keep happening.

    phkahler 1 hours

    >> Tech moves too fast and if we move too fast without doing review like 5-10 times, this will keep happening.

    Tech that becomes infrastructure like web servers doesn't move so fast and it shouldn't. Most people and companies should be relying on relatively tried and true software, so this phase of AI finding vulnerabilities in it should pass and things could get better.

    mynameisvlad 2 hours

    I would hope you know that no matter how many reviews, humans are fallible and miss things.

    cute_boi 1 hours

    AI agents are also fallible? So, what do you think we should do?

    mynameisvlad 1 hours

    Yes, AIs are fallible. Yes, humans are fallible. Nobody said differently.

    That's orthogonal to the point I'm making which is that no amount of reviews is going to make every single bug go away. Because, once again, humans and AI are fallible.

    chpatrick 1 hours

    The difference is that the AI doesn't get tired so you can review everything.

    g-b-r 15 minutes

    Except that it's very far from guaranteed to find everything, and especially everything that humans would find easily.