• Decronym@lemmy.decronym.xyzbot accountEnglish
    11 hours

    Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:

    Fewer Letters More Letters
    MECO Main Engine Cut-Off
    ~ MainEngineCutOff podcast
    SECO Second-stage Engine Cut-Off
    nginx Popular HTTP server

    3 acronyms in this thread; the most compressed thread commented on today has 7 acronyms.

    [Thread #171 for this comm, first seen 19th Nov 2026, 17:30] [FAQ] [Full list] [Contact] [Source code]

  • 3 days

    WHY do all new vulnerabilities have to use this inane naming scheme? These are grown-up problems. Can we use grown-up names?

    If someone finds another vulnerability in Nginx that gives root access, will it be called NGINX3root or NGINX2root2?

    (Yes, I know this is a petty complaint)

    • 2 days

      will it be called NGINX3root

      Only if the next one targets http3 instead of http2 😉

        • 2 days

          It’s explicitly exploiting the http2 flow control and neither 1.1 (the link above even suggests deactivating http2 as a temporary measure) nor –afaik– http3 (which works differently just by design principle) are affected.

            • 1 day

              I assumed we are talking about the title specifically.

              Crashing your service with an exploit depending “on conditions beyond the attacker’s control. Additionally, attackers can execute code on systems with Address Space Layout Randomization (ASLR) disabled” that “may allow remote attackers to cause a denial-of-service (DoS) on the NGINX system or to possibly trigger a code execution” may be a critical issues, too, but is not exactly the same thing as a proven way to get root access.

              • this CVE is also listed on the page linked in the post. and the root privileges are gained through a linux vulnerability, the nginx cves dont give root they just allow arbitrary code execution

  • 2 days

    On the bright side, nobody in the company ever took me seriously when I talked about security, but now they seem more willing to hear me out 🤷

    • Yeah, I was treated like Chicken Little because I was complaining about how shit our security was.

      Now, it is just “secure us and our vibe coded bullshit!!!”

      I am spending more time hacking our systems than it took to vibe code the shit they were rubbing peanut butter over their chest about.

      But not much longer.

      In fact, it is hilarious when the dude next to me vibe codes a tool, announces it in chat, and I immediately take it down. That’s happened twice, no botnet, or we now like to joke, full homo. “Sapiens Sapiens, stop making it sound gay.”

      For context, this was when I brought down an app another coworker had vibe coded with a localized LLM who I don’t think should be allowed to use a computer.

      Seriously, it took me 30 minutes to explain that I replaced the black ink cartridge in the printer, and he is good to print now. FML.

  • Just fyi, the nginx vulnerabilities are all impractical to use. The bugs are use after free, which will almost definitely lead to a crash in the worker process and have them be restarted.

    That itself would make it about as bad as the mp-tcp style expoits lately, but it’s even weaker. If you could keep trying, you could strap an llm into figuring out a specific machine and after tons of compute eventually get out data or take controll of the nginx-owned process.
    But, the restarts should restart that process, so I don’t see almost any risk unless you have address randomization disabled, which would be highly unusual.

    Unless I am missing something here, I see a bigger risk with an unmentioned loop that was also fixed in nginx. That one lets you make a worker thread hang, so you can disable a server until someone notices and restarts nginx. That ddos affects servers with tls1.3 support.

    Also their “2root” is just a completely unrelated kernel bug they bundled for marketing, which is pissing me off tbh. All of this “security research” for marketing is the worst possible contradictory incentive. You wanna release as poorly as possible to maximize fear mongering.
    They didn’t even release the bug, for all we know is as convoluted to use as the mp-tcp stuff and affects basically noone. Not that the nginx side is exploitable.

      • Well, as people write or update code they introduce new bugs, so if I don’t upgrade I don’t get any new bugs and Code Red is already dead.

        And besides, who went wrong with Microsoft? /s