On this page (7 sections)
Ubuntu has published security notice USN-9036-1 for ca-certificates-java, the package that keeps Java's certificate keystore in step with the operating system's list of trusted certificate authorities (CAs). According to the Ubuntu notice, the synchronization did not work properly in certain system languages, so CA certificates that had been removed from the system bundle were not removed from the Java keystore.
If you run Java applications on Ubuntu servers, such as application servers, build agents or services that make outbound HTTPS calls, this is worth a quick look. The notice is short, and a lot of detail is not yet public, so this article separates what is confirmed from what is not.
What happened
The Java platform keeps its own keystore of trusted CAs, in the JKS format. On Debian-family systems, the ca-certificates-java package fills that keystore from the system CA list, so Java programs trust the same authorities as the rest of the system. When the system list changes, the keystore is supposed to change with it.
Per the Ubuntu notice, that sync was faulty under certain system languages. Removals did not carry over: a CA taken out of the system bundle could remain in the JKS keystore. The update fixes the behavior and resyncs the keystore with the system list.
Why it matters
A CA is removed from a system bundle for a reason, usually because it is no longer trusted. Reasons can include a compromise, misissuance or a policy decision by the platform. If Java still trusts that CA, certificates it issued can still validate for Java programs, even though the rest of the system rejects them.
The practical impact depends on which CAs were removed on your system and whether any Java application there connects to a server presenting a certificate from one of them. The notice does not name any specific CA, so we cannot say which systems, if any, were meaningfully affected.
Who is exposed
- Ubuntu servers and workstations with ca-certificates-java installed, which is typical wherever a Java runtime is installed from Ubuntu packages.
- Systems running with a non-English system language, since the notice ties the fault to certain system languages. The notice does not list which languages.
- Systems where CA certificates were removed from the system bundle, for example by an update to the ca-certificates package or by an administrator.
Containers and images built on Ubuntu may carry the same package. They need a rebuild or an in-image update, not just an update on the host.
How to check your systems
The commands below are read-only. This one lists the installed version of the package on Ubuntu, so you can compare it with the fixed version shown in the notice for your release:
apt-cache policy ca-certificates-javaLook at the Installed and Candidate lines. If Candidate is newer than Installed, an update is waiting. This command shows the system language settings, which matter because the fault was tied to certain languages:
localeIf you want to inspect what Java currently trusts, the keytool utility that ships with the JDK can list keystore entries. The path to the keystore varies by Java version and distribution, so confirm it on your own system before running it, and compare the result against the system CA list in the same environment.
What to do now
- Open the Ubuntu notice USN-9036-1 and note the fixed package version for each Ubuntu release you run.
- Inventory hosts, containers and images that have ca-certificates-java installed.
- Install the updated package through your normal update process, starting with systems that make outbound HTTPS calls to third parties.
- Rebuild container images that bundle the package, then redeploy them.
- After updating, confirm the installed version matches the fixed one using apt-cache policy.
- Restart long-running Java services if your change process requires it, since a running JVM may have loaded the old trust store at startup.
On Ubuntu, a standard package update for just this package looks like this. It refreshes package lists, then upgrades only the named package:
sudo apt-get update
sudo apt-get install --only-upgrade ca-certificates-javaThe notice says the update resyncs the keystore with the system CA list. That is the documented fix, and we have no further detail on how the resync is performed beyond that.
Monitoring afterwards
Trust store drift is easy to miss because nothing visibly breaks. A few habits help:
- Subscribe to Ubuntu security notices for the releases you run, and treat trust-related packages like any other security update.
- Compare the Java trust store with the system CA list on a sample of hosts after CA-related updates.
- Watch the certificates your own public sites present, including expiry and issuer changes. A free SSL certificate checker can help for a quick look, and certificate and DNS monitoring can alert you when something changes.
- Keep outbound connections from Java services limited to the destinations they need, so an unexpected certificate chain stands out.
For wider habits around keeping server software current, see our guide to small business website security.
What we do not know yet
At the time of writing, this story rests on a single primary source, the Ubuntu notice. It does not include a CVE, a CVSS score, a list of affected releases, the languages involved, or any report of exploitation. We will not guess at these. Treat this as a correctness and hygiene fix that is worth applying promptly, and revisit the notice if Ubuntu updates it.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
