News for hackers. Stuff that matters.
Re:Java4Shell: RCE in OpenJDK when processing Base64 by ozgrakkurt on Tuesday November 17, 2026 @08:13PM (#50540609)
Not even fuzzing these things are criminal in 2026.

Is it difficult to just go through Java, nodejs etc. Base64/hex/.. implementations and fuzz them all?

Does anyone know why this would be missed?

Re:Java4Shell: RCE in OpenJDK when processing Base64 by knapsack-dev on Tuesday November 17, 2026 @08:42PM (#50540814)
Maybe the fuzzer wasn't running on the CPUs that were affected
Re:Java4Shell: RCE in OpenJDK when processing Base64 by jooops1 on Tuesday November 17, 2026 @08:57PM (#50540931)
Then you have coverage metrics showing that.
Re:Java4Shell: RCE in OpenJDK when processing Base64 by saagarjha on Wednesday November 18, 2026 @07:08AM (#50545311)
Assembly is a hard attack surface to fuzz since it’s not easy to instrument
Re:Java4Shell: RCE in OpenJDK when processing Base64 by ozgrakkurt on Wednesday November 18, 2026 @08:33AM (#50546120)
From what I understood it is generated by the JIT compiler and they don't fuzz JIT compiler output.

I am fairly sure it should still be possible to fuzz this by fuzzing the jit compiler. I understand it is not as easy as just fuzzing a regular function though.

It is even easier than fuzzing the JIT compiler in this case imo since it just inserts a fixed block of code which can be fuzzed seperately.