mraible opened a new pull request, #311:
URL: https://github.com/apache/roller/pull/311

   Java4Shell (CVE-2026-114938, https://calif.io/java4shell/) is an 
out-of-bounds write in HotSpot's Base64 decoding intrinsic on x86-64 processors 
with AVX-512 VBMI, in OpenJDK 17.0.6 and later until the November 2026 updates. 
It's a JVM bug, so Roller can't fix it, but its image and docs can help sites 
until their JDK is patched.
   
   - The Docker image sets `CATALINA_OPTS="-XX:-UseBASE64Intrinsics"`, which 
turns off the affected intrinsic and only costs Base64 speed. The option is 
accepted on ARM64 too (checked on an aarch64 Temurin 25.0.5 JVM), unlike 
`-XX:UseAVX=2`, which an ARM JVM refuses.
   - The install guide's Java requirement says to keep the JDK updated and, 
until then, to start the server with that option, for example in Tomcat's 
`CATALINA_OPTS`.
   - CHANGES has an entry under "Build and packaging", including that a 
`CATALINA_OPTS` passed to the container replaces the default.
   
   Where Roller's request handling reaches `java.util.Base64` before login, for 
reference: XML-RPC `<base64>` values (when XML-RPC is on), Spring Security's 
remember-me cookie (when remember-me is on), and, with #300, the login form's 
`_csrf` value, which Spring's XOR token handler decodes. AtomPub Basic auth 
uses commons-codec's decoder, which isn't affected.
   
   The UI test jobs for oidc and db-oidc build and start this image, so they 
check that Tomcat starts with the option.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to