Java4Shell Vulnerability For OpenJDK Java That Can Lead To Remote Code Execution

Java4Shell was publicly disclosed this afternoon as the latest high profile security vulnerability in the age of AI and LLMs. Java4Shell amounts to being a memory corruption vulnerability within OpenJDK's Base64 decoder that can lead to remote code execution. The CVSS 4.0 score comes in at 9.2 out of 10, a critical level. This base64 snafu can lead to pre-authentication remote code execution in the likes of Keycloak, Jira, Confluence, JFrog, Jenkins, and PingFederate. Or post-authentication RCE in the likes of Apache Kafka, Solr, ElasticSearch, Gerrit, Netflix Spinnaker, and others. Java4Shell comes down to a bug in the AVX-512 optimized Assembly code for Java's Base64 decoding: "To speed up Base64 decoding, OpenJDK uses specialized AVX-512 VBMI instructions on supported x86-64 processors. The bug sits in the hand-rolled assembly code that handles the final few characters. For the 65-character input above, OpenJDK allocates a 50-byte result array. After decoding the first 64 characters, the routine mishandles the stray = and calculates a negative output length. That invalid length becomes a full 64-byte write, sending 62 bytes past the end of the array. Java eventually rejects the input, but by then neighboring objects may already be corrupted." More details on Java4Shell can be found via the announcement. This is patched by Oracle with the critical security patch update advisory.

Original Source

Read the full article at Phoronix →

KhanList aggregates and links to publicly available news content. We do not host full articles from third-party sources. Always verify important information with original sources.