A new Java flaw lets attackers take over company servers, so patch now
A flaw in the free core of Java can let attackers take over servers running popular business tools. Oracle released the fix on 17 November, and companies running Java should apply it now.
The short version
- A serious flaw has been found in OpenJDK, the free core of Java that most companies run. It can let an attacker with no password take over a server.
- Oracle released the fix on 17 November. The flaw was first reported publicly in June, but a proposed fix was never applied until researchers showed attackers could use it.
- If your company runs Java on recent Intel or AMD server chips, ask your IT team to update it this week.
What happened
Java is one of the oldest and most widely used ways to build business software. Much of it runs on OpenJDK, the free version of Java that sits underneath products from many vendors.
The flaw sits in a small part of Java that handles a common text format called Base64. Base64 is a common way to turn files and login details into plain text. Ordinary features like logins and file uploads use it all the time.
A carefully crafted piece of text can make that code break out of its limits. An attacker can then read private data on the server, or take control of it. The research firm that disclosed the flaw scores it 9.2 out of 10, which counts as critical.
The researchers showed working attacks, without needing a login, on several popular business tools. They include Jira, Confluence, Jenkins and Keycloak, among others. With a login, they also took over popular tools that companies use to move and search data, such as Elasticsearch. They say the list is not complete.
The flaw affects OpenJDK 17.0.6 and newer, and the Java versions built from it. That includes Oracle's own Java and the versions made by Amazon, Microsoft and Red Hat.
There is one limit. The faulty code only runs on certain newer server chips. In practice that means recent Intel Xeon server chips and AMD chips from the Zen 4 generation onward. ARM-based servers are not affected.
What is actually new
The bug itself is not new. A Java user hit it in June and reported the crash. In September, an engineer found the cause and proposed a fix. That fix was closed without being merged.
On 24 October, a researcher asked an AI coding assistant, OpenAI's Codex, to look for weak spots in Java. It found this bug within an hour. The researcher built the first working attack two hours later, and the AI work cost less than $200.
The researchers then reported it to Oracle with proof that it could take over real products. Oracle fixed it and released the patch on 17 November, as part of a security update with 655 fixes across its products.
The researchers say they saw the same thing with an earlier flaw they found in PHP. The bug was already known, but it was only patched once someone proved it could be exploited. AI is making that proof much faster and cheaper to produce.
What it means for companies in Indonesia
The researchers point out that banks and telecom companies lean heavily on Java. That describes many of Indonesia's largest companies. Many also run the tools named above.
The researchers are holding back their ready-made attacks on specific products until people have had time to update. That gives you a short window. Attackers with AI tools can now rebuild such attacks quickly from the public details.
Cloud providers are already moving. Databricks, for example, says it switched off the faulty code on its platform and restarted affected systems to do it. It says customers on its fully managed service get the patched version automatically. Customers who run their own Databricks servers need to restart them.
Software you buy is a blind spot. Many products ship with their own copy of Java inside. Updating Java on your servers does not update those copies, so the vendor has to send a patch.
What to do
- Ask IT for a list of every system running Java 17 or newer on Intel or AMD servers.
- Apply Oracle's or your Java vendor's November update, starting with systems reachable from the internet.
- Where you can't update yet, ask engineers to switch off the fast decoder with a start-up setting. The researchers' write-up explains how.
- Ask the vendors of the business tools you run on Java when their patched versions will ship.
- Check whether your cloud providers have already patched, and whether you need to restart anything yourself.
- Treat this as a test of how fast you can patch. More flaws found with AI will follow.
