Someone reported java4shell bug in September 2026

(github.com)

129 points | by notmine1337 4 hours ago

8 comments

  • black3r 20 minutes ago
    The very first referenced issue in that PR discussion sheds a bit more light on this: https://github.com/adoptium/adoptium-support/issues/1480

    This PR's author says there on October 1st: "Got an email from Oracle asking me to NOT proceed with a PR until receiving approval." and then on October 28th: "It's taken over by Oracle. Nothing required from us."

  • wood_spirit 1 hour 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?
    • dlenski 19 minutes ago
      I don't think that's a reasonable implication at all.

      There are lots of bugs in lots of software, and lots of them get ignored when reported.

      I personally aware of multiple security vulnerabilities in major pieces of software that everyone has heard of, which I very quickly and easily stumbled on while working on this software as an AWS engineer several years ago. I had never used an LLM of any kind at the time.

      I presented my findings both internally and externally, and the reactions ranged from shrugs to delays to hostility towards me for "getting distracted" or "being overly negative."

      Those bugs that I discovered still exist, last time I checked.

    • cryptonector 56 minutes 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]?

      For the second question, I suspect it's because they were told a different fix was coming.

      • jakewins 30 minutes ago
        Why it was closed, surely, was because the only reaction to the PR was a bot saying it will automatically close the PR soon because of inactivity?

        I know I have opened a lot of PRs where the only result is I get bot spam in my email and no project reaction, so I close the PR to stop the bot spam; if nobody from Oracle has reacted in 2 months it seems unlikely anyone will.

        Nowadays I’ve stopped opening “cold-call” PRs like this. I find a way to chat with a maintainer first and anchor what I want to do (“I hit this bug, would you take a PR to fix it? I was thinking it could be solved by x, would that work?”

        Much much better outcomes that way.

      • philipwhiuk 27 minutes ago
        > why was this not a secure vulnerability report, why was it public?

        Because it was seen as a crash not an RCE. AI's power has been chaining simple crashes into exploits. But that's not generally going to be true.

        • wat10000 15 minutes ago
          I'd be surprised if that's what happened. The instant I see "corrupting the heap" I assume it's a serious vulnerability unless proven otherwise. AI is taking it to another level, but the days of dismissing memory corruption as unexploitable died years before.
  • darkamaul 53 minutes ago
    We will never know, but there is a chance that the Calif's researcher model decided to look at the open and closed issues / PRs of the repo.

    Nonetheless, being able to understand the criticality of a finding, and how to exploit it are other skills, that still require supervision.

  • rzmmm 1 hour 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 1 hour 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.

      • xmodem 55 minutes ago
        "I worked on the physics engine, tests, via widely accessible libraries." is a nonsensical sentence as written, but a colleague who told me they had done this would be telling me a vastly different thing to if they had told me they had compiled the source code to a physics engine.

        There is a massive difference between prompting "security audit this codebase, make no mistakes", performing an in-depth agent or LLM-assisted focused search for security relevant code, or otherwise manually reviewing code as we did in the pre-LLM era. It behooves us to be honest about our own personal contribution to our output - both towards others and to ourselves.

        • tkz1312 27 minutes ago
          I don't disagree with you necessarily, and I do think it a good practice to disclose how much of a contribution was llm generated, but regarding the difference an individual makes, I see a huge gap between different colleagues in how well they are able to use llms and the quality of the results they are able to produce with them, so I am increasingly inclined to view them as something closer to a compiler or SMT solver than a contributor in of themselves.
      • LoganDark 1 hour 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.

      • wat10000 23 minutes ago
        Is it really fair to say that I did something when my contribution was typing straightforward English prose for thirty seconds and then letting it run?

        Your hypothetical makes the opposite point from what you intend. If someone in 2015 said that they worked on a physics engine, and all they did was run the compiler on existing code, we'd laugh them out of the room. Pointing an existing computer program at existing work doesn't count as doing very much.

      • p-e-w 1 hour 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 1 hour 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"
  • InsidiousWombat 1 hour 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 1 hour ago
      Agreed, but in this case it looks like the submitter closed it? What's that about?
      • pimterry 16 minutes ago
        They closed themselves immediately after the stale bot pinged to say it was going to be closed automatically. If you're not that investigated in a PR for a niche corruption bug, you open it and nobody responds for two months, when you get notified about it it's pretty reasonable to just close and move on. Perfectly normal OSS contributor behaviour imo (especially in this new world where every project is drowning under AI contributions, and struggling to stay responsive).
        • toast0 4 minutes ago
          > you open it and nobody responds for two months, when you get notified about it it's pretty reasonable to just close and move on.

          Why invest more time to close it? The automation will do it for you.

      • dboreham 1 hour ago
        They knew about the fix coming?
        • cryptonector 54 minutes ago
          That's my guess. But also opening a public issue was a faux pas.
          • dlenski 15 minutes ago
            > But also opening a public issue was a faux pas.

            Sorry, but why?

            Why should someone discovering a bug in an enormously complex piece of software have any responsibility for assessing the security implications of that bug?

            If the maintainers wanted to make it private they could have done so.

          • philipwhiuk 26 minutes ago
            At the time maybe he assumed it was just a crash.
    • dboreham 1 hour ago
      A project with auto bug close signals to me that it is badly managed and hence should be used with caution.
    • wat10000 18 minutes ago
      The bot auto-closes issues that have been inactive for 16 weeks. The CVE was published at about 10 weeks in. The auto-close bot was completely irrelevant to this. The issue wasn't that it got auto-closed (it didn't) but that nobody from the project looked at the PR. That's a hard problem to solve, because any big project has a lot of volume and it's easy to miss things. It's unfortunate but a fact of life that you can't just toss up a PR and expect anyone to automatically look at it.
      • fn-mote 2 minutes ago
        > you can't just toss up a PR and expect anyone to automatically look at it.

        Except soon you can expect LLM triage to be standard.

        We would then find out if enough tokens would be invested in this one to figure out it was important, but any look is better than none.

    • cryptonector 1 hour ago
      It wasn't auto-closed.
    • frangonf 1 hour 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 1 hour ago
      Grab a billion tokens and farm auto-closed GitHub issues. Become HN famous for a day.
  • fulafel 2 hours ago
    It's even titled buffer overflow.
  • yread 2 hours ago
    They even used the same example as Calif: AAA....A=.
    • Alifatisk 2 hours ago
      Using As when fiddling with the memory is common. Nothing unique to Calif.
      • rustyhancock 1 hour 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 1 hour 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 1 hour ago
          Today I learned that the Base64 Alphabet doesn't start with the numbers so A is 0 And 0 is 52.
      • layer8 1 hour 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).
  • elashri 2 hours ago
    This person is a member of OpenJDK organization and a contributer but not sure if he is oracle employee.
    • egorfine 1 hour ago
      None of this did help: nobody gave a flying f.
      • bobmcnamara 1 hour ago
        Someone probably gave a maintainer "the talk"