Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Cyborg)
  • No Skin
Collapse
Brand Logo

CIRCLE WITH A DOT

  1. Home
  2. Uncategorized
  3. There's serious panic being caused by AI discovered vulnerabilities behind the scenes, where those finding them are basically using them as marketing.

There's serious panic being caused by AI discovered vulnerabilities behind the scenes, where those finding them are basically using them as marketing.

Scheduled Pinned Locked Moved Uncategorized
14 Posts 10 Posters 0 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • gossithedog@cyberplace.socialG gossithedog@cyberplace.social

    CVE-2026-34486 - Tomcat

    - Only exploitable if a certain feature is used, if its endpoint is reachable and if port 4000 is available. It's pretty niche.

    gossithedog@cyberplace.socialG This user is from outside of this forum
    gossithedog@cyberplace.socialG This user is from outside of this forum
    gossithedog@cyberplace.social
    wrote last edited by
    #4

    CVE-2026-42945 - Nginx (otherwise branded Nginx Rift)

    It relies on a specific Nginx config to be vulnerable, and for attacker to know or discover the config to exploit it. To reach RCE, also ASLR needs to have been disabled on the box.

    The PoC they've built specifically disabled ASLR, deploys a specifically vulnerable config and the exploit knows about the vulnerable config endpoint.

    Link Preview ImageLink Preview Image
    wdormann@infosec.exchangeW gossithedog@cyberplace.socialG 2 Replies Last reply
    0
    • misusecase@twit.socialM misusecase@twit.social

      @GossiTheDog I really want to hear your take on this because I’ve heard conflicting things about whether any of the vulnerabilities are serious or not.

      0xtero@ohai.social0 This user is from outside of this forum
      0xtero@ohai.social0 This user is from outside of this forum
      0xtero@ohai.social
      wrote last edited by
      #5

      @MisuseCase @GossiTheDog most of the stuff is just pure marketing fluff. Sure, AI is finding bugs. People are fixing them. This has been the case for a while now. Nothing new. Exploitable bugs still very rare. Catastrophic ones like Heartbleed nil, so far. It’s business as usual. The noise volume is up, quality of the signal seems about same as always.

      misusecase@twit.socialM 1 Reply Last reply
      0
      • gossithedog@cyberplace.socialG gossithedog@cyberplace.social

        CVE-2026-34486 - Tomcat

        - Only exploitable if a certain feature is used, if its endpoint is reachable and if port 4000 is available. It's pretty niche.

        mikesiegel@infosec.exchangeM This user is from outside of this forum
        mikesiegel@infosec.exchangeM This user is from outside of this forum
        mikesiegel@infosec.exchange
        wrote last edited by
        #6

        @GossiTheDog while they can certainly find some fun things, a number of the "vulns" are ridiculous "Oh this can be an RCE during full moons with ASLR disabled running on TRSDOS ported to ARM."

        The models don't really threat model well at all. I like @bagder 's approach of VULN-DISCLOSURE-POLICY.md

        1 Reply Last reply
        0
        • gossithedog@cyberplace.socialG gossithedog@cyberplace.social

          CVE-2026-42945 - Nginx (otherwise branded Nginx Rift)

          It relies on a specific Nginx config to be vulnerable, and for attacker to know or discover the config to exploit it. To reach RCE, also ASLR needs to have been disabled on the box.

          The PoC they've built specifically disabled ASLR, deploys a specifically vulnerable config and the exploit knows about the vulnerable config endpoint.

          Link Preview ImageLink Preview Image
          wdormann@infosec.exchangeW This user is from outside of this forum
          wdormann@infosec.exchangeW This user is from outside of this forum
          wdormann@infosec.exchange
          wrote last edited by
          #7

          @GossiTheDog
          (except fewer)

          1 Reply Last reply
          0
          • 0xtero@ohai.social0 0xtero@ohai.social

            @MisuseCase @GossiTheDog most of the stuff is just pure marketing fluff. Sure, AI is finding bugs. People are fixing them. This has been the case for a while now. Nothing new. Exploitable bugs still very rare. Catastrophic ones like Heartbleed nil, so far. It’s business as usual. The noise volume is up, quality of the signal seems about same as always.

            misusecase@twit.socialM This user is from outside of this forum
            misusecase@twit.socialM This user is from outside of this forum
            misusecase@twit.social
            wrote last edited by
            #8

            @0xtero @GossiTheDog Meanwhile

            1. AI coding agents are one of the factors contributing to shorter intervals between “vulnerability discovery” and “working exploit”

            2. Orgs can’t be bothered to patch known vulnerabilities in a timely fashion so a huge proportion of cyberattacks and their associated damage are down to bugs that have been known about (and left unpatched) for half a year or more

            1 Reply Last reply
            0
            • gossithedog@cyberplace.socialG gossithedog@cyberplace.social

              There's serious panic being caused by AI discovered vulnerabilities behind the scenes, where those finding them are basically using them as marketing. Automated vulnerability hype train again, basically.

              A thread on a few of them.

              robinsyl@meow.socialR This user is from outside of this forum
              robinsyl@meow.socialR This user is from outside of this forum
              robinsyl@meow.social
              wrote last edited by
              #9

              @GossiTheDog I already feel so "boy who cried wolf"ed about all the vulns

              1 Reply Last reply
              0
              • gossithedog@cyberplace.socialG gossithedog@cyberplace.social

                CVE-2026-42945 - Nginx (otherwise branded Nginx Rift)

                It relies on a specific Nginx config to be vulnerable, and for attacker to know or discover the config to exploit it. To reach RCE, also ASLR needs to have been disabled on the box.

                The PoC they've built specifically disabled ASLR, deploys a specifically vulnerable config and the exploit knows about the vulnerable config endpoint.

                Link Preview ImageLink Preview Image
                gossithedog@cyberplace.socialG This user is from outside of this forum
                gossithedog@cyberplace.socialG This user is from outside of this forum
                gossithedog@cyberplace.social
                wrote last edited by
                #10

                I will likely be one of the first people banging the drum to patch and mitigate if any of the recent AI vulns results in serious harm. Otherwise, keep calm and carry on patching as usual.

                nyanbinary@infosec.exchangeN F draeath@infosec.exchangeD 3 Replies Last reply
                1
                0
                • gossithedog@cyberplace.socialG gossithedog@cyberplace.social

                  There's serious panic being caused by AI discovered vulnerabilities behind the scenes, where those finding them are basically using them as marketing. Automated vulnerability hype train again, basically.

                  A thread on a few of them.

                  womble@infosec.exchangeW This user is from outside of this forum
                  womble@infosec.exchangeW This user is from outside of this forum
                  womble@infosec.exchange
                  wrote last edited by
                  #11

                  @GossiTheDog I'd be willing to bet that if they paid real humans the same amount of money as the true cost of running the LLM, they'd find more and better bugs.

                  1 Reply Last reply
                  0
                  • gossithedog@cyberplace.socialG gossithedog@cyberplace.social

                    I will likely be one of the first people banging the drum to patch and mitigate if any of the recent AI vulns results in serious harm. Otherwise, keep calm and carry on patching as usual.

                    nyanbinary@infosec.exchangeN This user is from outside of this forum
                    nyanbinary@infosec.exchangeN This user is from outside of this forum
                    nyanbinary@infosec.exchange
                    wrote last edited by
                    #12

                    @GossiTheDog but but but, how else am I supposed to market magic box triage-as-a-service

                    1 Reply Last reply
                    0
                    • gossithedog@cyberplace.socialG gossithedog@cyberplace.social

                      I will likely be one of the first people banging the drum to patch and mitigate if any of the recent AI vulns results in serious harm. Otherwise, keep calm and carry on patching as usual.

                      F This user is from outside of this forum
                      F This user is from outside of this forum
                      fatalisticcritic@cyberplace.social
                      wrote last edited by
                      #13

                      @GossiTheDog and that's why I'm here. Thanx for keeping us calm.

                      1 Reply Last reply
                      0
                      • gossithedog@cyberplace.socialG gossithedog@cyberplace.social

                        I will likely be one of the first people banging the drum to patch and mitigate if any of the recent AI vulns results in serious harm. Otherwise, keep calm and carry on patching as usual.

                        draeath@infosec.exchangeD This user is from outside of this forum
                        draeath@infosec.exchangeD This user is from outside of this forum
                        draeath@infosec.exchange
                        wrote last edited by
                        #14

                        @GossiTheDog ... also never turn off ASLR! Why would someone do that nowadays!?

                        1 Reply Last reply
                        0
                        • R relay@relay.infosec.exchange shared this topic
                          R relay@relay.publicsquare.global shared this topic
                        Reply
                        • Reply as topic
                        Log in to reply
                        • Oldest to Newest
                        • Newest to Oldest
                        • Most Votes


                        • Login

                        • Login or register to search.
                        • First post
                          Last post
                        0
                        • Categories
                        • Recent
                        • Tags
                        • Popular
                        • World
                        • Users
                        • Groups