On this page (7 sections)

Canonical has published USN-9001-2, an update for the ca-certificates and ca-certificates-java packages on Ubuntu 18.04 LTS and Ubuntu 20.04 LTS. It is the follow-up to USN-9001-1 and brings the same fix to those two older releases.

The problem is that the Java (JKS) keystore was not kept in sync with the system CA list. If you run Java applications on these Ubuntu releases that make outbound TLS connections, this is worth a look. Note that the fix is delivered through Ubuntu Pro, which the notice marks as required for these releases.

What happened

According to the notice, the ca-certificates JKS integration was not working properly. As a result, CA certificates that had been removed from the system bundle were not being removed from the JKS keystore. The update corrects the feature and resyncs the keystore with the system CA certificates list.

USN-9001-1 originally fixed this in ca-certificates and ca-certificates-java. USN-9001-2 provides the corresponding packages for Ubuntu 18.04 LTS and 20.04 LTS, which are in extended security maintenance (the version strings carry an esm suffix).

What we know and do not know

The notice is short. It does not give a CVE identifier or a severity rating, and it does not say that the issue is being exploited. Only one source, Ubuntu's own notice, covers this story so far, so there is no independent confirmation or additional technical analysis to draw on. We will not guess at details the vendor has not published.

  • Known: the JKS keystore did not drop CA certificates that were removed from the system bundle.
  • Known: the fix resyncs the keystore with the system CA list.
  • Not stated: which specific CAs were affected, how long the mismatch existed, or whether any attack relied on it.
  • Not stated: a CVSS score or any exploitation status.

Why this matters in plain terms

The system CA bundle is the list of certificate authorities your server trusts when it validates TLS connections. When a CA is distrusted and removed from that list, you expect every consumer of the list to stop trusting it. Java applications often use their own keystore in JKS format rather than reading the system bundle directly. If that keystore is not updated, Java software can keep trusting a CA that the rest of the system has already dropped.

This explanation of the weakness class is general background, not a statement from the notice about how any particular CA or application was affected. The practical point is that a stale trust store undermines the purpose of removing a CA in the first place.

Who is affected

Based on the notice, the affected systems are Ubuntu 18.04 LTS and 20.04 LTS with the ca-certificates and ca-certificates-java packages installed. Servers that run Java applications such as application servers, build tools, or services that call external HTTPS APIs are the most realistic place the Java keystore matters. Systems with ca-certificates but no Java are less likely to see any practical effect, though a standard update is still recommended.

The listed fixes are marked as available with Ubuntu Pro. The notice states Ubuntu Pro is free for up to five machines. If you do not have Pro enabled on these releases, you will not receive the fixed package versions through normal updates.

How to check your exposure

The following read-only command lists the installed versions of both packages on Debian-based systems such as Ubuntu. Run it on each server and compare the output with the fixed versions in the table below.

Show installed ca-certificates and ca-certificates-java versions (Ubuntu 18.04 / 20.04)Shell
dpkg -l ca-certificates ca-certificates-java

If a package is not installed, dpkg reports that no packages match, which means that part does not apply to the host.

Fixed package versions from USN-9001-2
Ubuntu releasePackageFixed version
20.04 LTS (focal)ca-certificates20240203~20.04.2ubuntu0.1~esm3
20.04 LTS (focal)ca-certificates-java20190405ubuntu1.2~esm1
18.04 LTS (bionic)ca-certificates202402031ubuntu0.18.04.2+esm4
18.04 LTS (bionic)ca-certificates-java20180516ubuntu1~18.04.3+esm1

What to do now

The notice says a standard system update makes all the necessary changes. The steps below follow that guidance.

  1. List your Ubuntu 18.04 and 20.04 hosts and note which ones run Java workloads.
  2. Confirm Ubuntu Pro is enabled on those hosts, since the fixes are delivered through it.
  3. Run a normal package update and upgrade, then verify the installed versions match the table above.
  4. Restart long-running Java services so they pick up the refreshed keystore, after planning for the brief interruption.
  5. Re-test outbound HTTPS connections from your Java applications to confirm nothing you rely on broke.
  6. Record the update in your patch log and plan a move off releases that depend on extended maintenance.

This pair of commands refreshes the package index and upgrades only the two affected packages on Ubuntu 18.04 and 20.04. Afterward, run the dpkg check above and look for the fixed version strings.

Update only the two affected packages (Ubuntu 18.04 / 20.04, requires Ubuntu Pro access)Shell
sudo apt update
sudo apt install --only-upgrade ca-certificates ca-certificates-java
Caution. Restarting Java services interrupts them. Do it in a maintenance window, and test on a staging host first if the application depends on a custom keystore, because the update resyncs the JKS keystore with the system CA list.
Tip. If your application uses a custom truststore that you manage by hand, the system update will not change it. Review that file separately and remove any CAs you no longer want to trust.

Detection and monitoring afterwards

After patching, watch for TLS validation errors in your Java application logs. A connection that now fails may have depended on a CA that was removed from the system bundle and is no longer trusted. Treat that as a signal to check the remote service's certificate chain rather than re-adding the CA.

You can also review the certificates your own sites present with the free SSL certificate checker, and Webforta Monitor can alert you to certificate changes on your public hostnames. These cover what your sites serve to visitors, not the trust store inside your servers, so they complement patching rather than replace it.

For wider context on keeping servers current, see our other Ubuntu notices such as USN-9008-1: libnfs Out-of-Bounds Write and USN-9007-1: FreeRDP Vulnerabilities.

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.

  1. USN-9001-2: ca-certificates update | Ubuntu security notices | Ubuntuubuntu.com ·
  • Ubuntu
  • ca-certificates
  • Java
  • TLS
  • Ubuntu Pro
  • USN