Independent & educational platform Not a government body. No link or affiliation with any government organisation. Made for learning only. Test only systems you own or are authorised to test. Become a Partner or Sponsor → Full disclaimer
vulnerability Imported story

A new critical Java hole illustrates the enterprise IT visibility problem

Source: CSO Online · Published · Last checked 1 hour ago · 3 min read
A new critical Java hole illustrates the enterprise IT visibility problem
Image: CSO Online
Read original source ↗ (www.csoonline.com)

Publisher excerpt From CSO Online

When cybersecurity research firm Calif published details Tuesday of a potentially major Java security flaw, dubbed Java4Shell, it described an unauthenticated attacker’s ability to read Java heap memory, steal private keys, tokens, and session secrets, and reach remote code execution (RCE). With Java being all-but-ubiquitous in today’s enterprise, coupled with the inability of CISOs to have visibility into every instance of it in their estate, this means that the bug could be a big problem for IT. Java, which has had its fair share of cybersecurity issues lately, is well-known for safely handling memory. That is why a Java bug affecting memory management is so dangerous. Java4Shell, tracked as CVE-2026-114938, is a vulnerability in the OpenJDK x86-64 Base64 decoder that scores 9.2 in severity (Critical) under CVSS 4.0, Calif said. Oracle assigned it a lower rating of 8.1 (High) using CVSS 3.1. Calif explained in its post describing the issue that Base64 is a common way of representing binary data as text. “It is used in authentication protocols, to encode file uploads, and to deliver network messages,” it wrote. “To decode Base64 faster, OpenJDK uses specialized x86-64 CPU instructions to process many bytes at once. We discovered a bug in optimized machine-level code that lets malformed input overwrite neighboring memory. With careful exploitation, the corruption can reveal sensitive memory, as Heartbleed did, or lead to remote code execution.” It said that the corruption can be triggered by a string of just 64 “A” characters followed by a single equals sign (=); in older OpenJDK 17 versions, 128 “A” characters are required before the equals sign. “Memory corruption is the most common class of vulnerability on the internet,” Calif said. “But one of Java’s biggest selling points is memory safety. Java manages memory on developers’ behalf and checks memory accesses, protecting applications from the memory-corruption bugs common in other software. But like PHP and many other technologies, much of Java itself is written in low-level languages like C, C++, and, in this case, assembly, where memory corruption is still a part of life.” Assessing the bug’s potential for exploit is complicated because triggering it requires a hardware accelerated decoding function that’s used on some x86-64 processors supporting AVX-512 VBMI instructions. And fixing it requires patches from a lengthy list of vendors; just installing Tuesday’s patch from Oracle, which owns Java, is not going to do the trick. Potential damage ‘extreme’ Noah Kenney, principal consultant at Digital 520, said the potential damage from an unpatched instance of exposed Java is extreme. “The researchers were able to read Java heap memory before they achieved code execution, so an attacker may be able to steal tokens, credentials, or keys from those systems. That access can remain useful even after the vulnerable server has been patched,” Kenney said. “Any unexplained crashes on an expo…

Excerpt only, shown with attribution. This content belongs to the original publisher and has not been independently verified by CyberSecurity.pk.

Related CVEs

Reference: CSO Online — www.csoonline.com ↗

Related news