• Ooops@feddit.org
    link
    fedilink
    English
    arrow-up
    1
    ·
    2 days ago

    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.

      • Ooops@feddit.org
        link
        fedilink
        English
        arrow-up
        1
        ·
        22 hours ago

        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.

        • WhyJiffie@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          1
          ·
          2 hours ago

          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