Re:Java4Shell: RCE in OpenJDK when processing Base64
by CAP_NET_ADMIN on Tuesday November 17, 2026 @07:01PM
(#50540033)
Vectorized base64 can reach speeds in the proximity of memory copy.
I've easily reached a point where it was worth it to go AVX route in my "for funsies" game that I'm making.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by CAP_NET_ADMIN on Tuesday November 17, 2026 @07:04PM
(#50540060)
Just checked, the scalar version reaches around 1-2GB/s when decoding, optimized it gets to 4GB/s, AVX-512 VBMI version reaches 40-55GB/s.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by bullen on Tuesday November 17, 2026 @07:06PM
(#50540082)
Interesting, what game are you making?
Re:Java4Shell: RCE in OpenJDK when processing Base64
by CAP_NET_ADMIN on Tuesday November 17, 2026 @07:23PM
(#50540237)
Large scale tower/base defense with time rewind mechanics and user-generated structure templates.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by bullen on Tuesday November 17, 2026 @08:51PM
(#50540892)
So where do you need 40GB/s of base64?
Re:Java4Shell: RCE in OpenJDK when processing Base64
by layer8 on Tuesday November 17, 2026 @07:51PM
(#50540434)
Your decoder implementation accepts all sorts of non-Base64 strings and decodes them to whatever. Among other things, it also accepts MIME Base64 (with line breaks and whitespace) and base64url strings, but decodes them to the wrong values. This is a classic example of insufficient input validation that can lead to parser mismatch vulnerabilities or worse.
http://move.rupy.se/file/base64.txt
If this part becomes the bottleneck; so I need to write a GPU accelerated version I'll eat my own hat.