News for hackers. Stuff that matters.
Re:Java4Shell: RCE in OpenJDK when processing Base64 by eyalitki on Tuesday November 17, 2026 @04:36PM (#50538534)
The fact that mainstream modules have such trivial bugs in logic that can be fully covered by testing is staggering. It is about time software developers will have proper test coverage for their code, at least for basic "unit" modules. Maybe we can even name a testing philosophy to match it.
Re:Java4Shell: RCE in OpenJDK when processing Base64 by ajasmin on Tuesday November 17, 2026 @04:59PM (#50538825)
Finding these kind of bugs would have required fuzzing and some kind of bound checking canaries. Not sure all bound checkers work on the hand-optimized assembly.

Or as it turns out an LLM! Not clear whether their agent spawned any classic tools...

Re:Java4Shell: RCE in OpenJDK when processing Base64 by stassats on Tuesday November 17, 2026 @09:51PM (#50541256)
> bound checking canaries

I used memory protection for that. mmap a page, align the string start/end to the page boundaries. Catches both bad reads and writes.

Re:Java4Shell: RCE in OpenJDK when processing Base64 by Noe2097 on Tuesday November 17, 2026 @05:03PM (#50538873)
Not sure this is as trivial as it seems. The bug triggers on a specific instruction set, on a precise input length, with a specific character at the end, and when on the hot path, and requires low level memory access checking to be detected.
Re:Java4Shell: RCE in OpenJDK when processing Base64 by spockz on Tuesday November 17, 2026 @05:43PM (#50539329)
For the finished jre yes. But one would hope these kind of checks are also run on a hand rolled decoder function. Fuzzing that one and finding logic bugs is a lot easier