Someone reported java4shell bug in September 2026

(github.com)

100 points | by notmine1337 3 hours ago

6 comments

  • wood_spirit 34 minutes ago
    So the implication is that the LLM that assisted the Calif researchers might have read this previous bug report and not independently discovered it?
    • cryptonector 1 minute ago
      Idk that u/notmine1337 meant that. I have questions:

      - why was this not a secure vulnerability report, why was it public?

      - why was this closed [by the submitter]?

  • rzmmm 31 minutes ago
    From califio: "I focused the audit on the JIT compiler, intrinsics, widely accessible APIs, and cryptography. Well, more precisely, I told Codex to look at those areas like any serious security researcher in 2026."

    Maybe simply a coincidence, but I would put my bets that the first person with the PR was also using Codex, and the model was exposed to the details of the bug.

    • rfgplk 19 minutes ago
      > From califio: "I focused the audit on the JIT compiler, intrinsics, widely accessible APIs, and cryptography. Well, more precisely, I told Codex to look at those areas like any serious security researcher in 2026."

      I have no idea why people keep talking like this. Probably because sadly most engineers lack the ego to back themselves up. Imagine if someone said this in 2015: "I worked on the physics engine, tests, via widely accessible libraries. Well, more precisely, I told my compiler to read the source code and compile it like any serious software engineer in 2026."

      Quit saying Codex/Claude/an LLM did something. They didn't. You did.

      • LoganDark 9 minutes ago
        > Quit saying Codex/Claude/an LLM did something. They didn't. You did.

        I think there's a vast difference between giving source code to a compiler (even a superoptimizing compiler) and giving a prompt to a language model. This distinction absolutely deserves to be called out and not swept under the rug. It doesn't make you any less responsible for what you submit, but it's courteous to your reviewers to be transparent.

      • p-e-w 10 minutes ago
        A frontier AI is nothing like a compiler. The litmus test is how much expertise was required to get it to find the results. If a basic prompt brings up an industry-shaking vulnerability of this caliber, then the human was at best a janitor.
      • NooneAtAll5 14 minutes ago
        no, it's more like "I worked on physics engine. Well, more precisely, I used already made library and never even looked at actual physics"
  • elashri 1 hour ago
    This person is a member of OpenJDK organization and a contributer but not sure if he is oracle employee.
    • egorfine 38 minutes ago
      None of this did help: nobody gave a flying f.
      • bobmcnamara 32 minutes ago
        Someone probably gave a maintainer "the talk"
  • InsidiousWombat 28 minutes ago
    Nice proof that the auto-close bots are literal cancer on project that make stuff worse.

    It was literal bug with provided fix. All it needed is someone to have a proper look.

    But someone clowned a bot under a visionary thought "if nobody looked it must not be important" and here we are

    • stickfigure 17 minutes ago
      Agreed, but in this case it looks like the submitter closed it? What's that about?
      • dboreham 6 minutes ago
        They knew about the fix coming?
    • dboreham 6 minutes ago
      A project with auto bug close signals to me that it is badly managed and hence should be used with caution.
    • cryptonector 14 minutes ago
      It wasn't auto-closed.
    • frangonf 5 minutes ago
      Even Duke gave up on the current state of software.

      Would it be better to have some Oracle gpus running the dukebot? Are the robobun and friends better at real triage/escalation? Could we automate the robobots to register the `java2root.com` domain on its own, release a blog post and post it in twitter/hn upon every successful security issue?

    • bombcar 15 minutes ago
      Grab a billion tokens and farm auto-closed GitHub issues. Become HN famous for a day.
  • fulafel 1 hour ago
    It's even titled buffer overflow.
  • yread 1 hour ago
    They even used the same example as Calif: AAA....A=.
    • Alifatisk 1 hour ago
      Using As when fiddling with the memory is common. Nothing unique to Calif.
      • rustyhancock 23 minutes ago
        Yes, especially in past decades when it's easy to spot 41414141 on the stack in a debugger.

        You might follow up with a De Bruijn/cyclic pattern and can see the overflow happen by step1 and precisely locate it by what replaces the A's.

        https://youtu.be/L2j90atBpRU?is=q6W_1eF4viMoKZEA

        Didn't the Alpine Linux bug also use A's for the exploit to login as root?

      • gruez 53 minutes ago
        Not to mention it's the first letter in the base64 alphabet, so if you want a bunch of zeroes, that's how you get it.
        • echoangle 21 minutes ago
          Today I learned that the Base64 Alphabet doesn't start with the numbers so A is 0 And 0 is 52.
      • layer8 48 minutes ago
        Except that in Base64 it’s not the alternating bit pattern of hex A (binary 0101), which is the property one uses it for in memory, but instead decodes to all-zeros (and is binary 01000001 in ASCII before decoding).