Ubuntu · Packages & updates

Receive security updates for every installed package, including universe (Ubuntu Pro esm-apps)

When it fails: Packages from universe are installed without Ubuntu Pro esm-apps. The Ubuntu Security Team does not commit to fix the universe packages of this system, so their vulnerabilities can stay open.

CB-UBU-PKG-014mediumactiveautomatedprofile serverprofile desktop-hardened

As released in v0.1.0 (beta). Current state.

Description

Ubuntu standard security maintenance covers the main and restricted components only. Packages of the universe component (and multiverse) get fixes from the community, on a best-effort basis, and many known vulnerabilities in universe stay unfixed. Expanded Security Maintenance for Applications (esm-apps), part of Ubuntu Pro, extends Canonical's security maintenance to universe, from the release of an LTS to the end of its ESM period.

pro security-status counts the installed packages per component and shows which Ubuntu Pro services are enabled. The control fails only when packages from universe are installed and esm-apps is not enabled. A system with packages from main and restricted only passes without Ubuntu Pro.

The check needs the Ubuntu Pro client (ubuntu-pro-client, installed by default on every release) and fresh package lists. A single universe package is enough to fail, for example qemu-guest-agent installed on virtual machines. Multiverse packages (not free software) are not counted.

Rationale

Universe holds most of the archive, including common server software (web and database servers, language runtimes, agents). A universe package installed for one need is as exposed as a main package, but without a commitment to fix it. With esm-apps, the fixes are published in the <codename>-apps-security pocket and installed by unattended-upgrades like the others.

Impact

Needs an Ubuntu Pro subscription for each system (free for a few personal machines). Without it, remove the universe packages or replace them with packages from main, a vendor repository or a supported snap. The esm-apps repository needs access to esm.ubuntu.com (or an internal mirror).

Setting

LocationUbuntu Pro client status (pro status, pro security-status)
DefaultNot attached to Ubuntu Pro, esm-apps disabled
RecommendedNo universe package installed, or esm-apps enabled

Audit

  1. Run pro security-status. If it reports no package from Universe/Multiverse, or only from multiverse (pro security-status --format json, num_universe_packages is 0), the control passes.
  2. Otherwise pro status must show the system attached and esm-apps enabled. pro security-status --esm-apps lists the universe packages concerned.

Automated: every check must pass. Scanners report each check by its id.

esm-apps

Installed universe packages and the esm-apps service, from pro security-status.

script: |
  command -v pro >/dev/null || { echo "Ubuntu Pro client (pro) is not installed"; exit 3; }
  j=$(pro security-status --format json 2>/dev/null) || { echo "pro security-status failed"; exit 3; }
  printf '%s' "$j" | python3 -c '
  import json, sys
  s = json.load(sys.stdin)["summary"]
  n = s.get("num_universe_packages", 0) + s.get("num_esm_apps_packages", 0)
  on = "esm-apps" in s.get("ua", {}).get("enabled_services", [])
  print("%d packages from universe, attached to Ubuntu Pro: %s, esm-apps %s" % (n, s.get("ua", {}).get("attached"), "enabled" if on else "not enabled"))
  sys.exit(1 if n and not on else 0)'

Remediation

  1. Attach the system to Ubuntu Pro: pro attach <token> (token from https://ubuntu.com/pro or the organisation's Ubuntu Pro account), or use an Ubuntu Pro image of the cloud provider, or Landscape.
  2. Run pro enable esm-apps if it is not enabled by the attachment, then apt-get update and apt-get upgrade to install the pending ESM fixes.
  3. Without a subscription, remove the universe packages that are not needed (pro security-status --esm-apps lists them), and document the remaining ones as an accepted risk in the tailoring file.

No automated fix: attaching needs the organisation's token, which must not be stored in the baseline.

References

Mappings

FrameworkIDRelationNote
NIST SP 800-53 Rev. 55.1.1SI-2partialCovers the vendor support of every installed package, a prerequisite for flaw remediation.
NIST SP 800-53 Rev. 55.1.1SA-22partialA universe package without esm-apps has no vendor commitment to security fixes.

How this control relates to the other framework's: equivalent, stricter, looser, partial or related.

Threats mitigated

  • related CB-UBU-PKG-009 Run an Ubuntu release that still receives security updates
  • related CB-UBU-PKG-010 Install only the packages the system needs

People and lifecycle

Authors
Verified2026-10-19 by Sn0wAlice on 20.04, Proxmox VM, Ubuntu 20.04 cloud image, kernel 5.4.0-216-generic. Fails on stock (qemu-guest-agent from universe, not attached to Ubuntu Pro); passes with a shimmed pro security-status reporting esm-apps enabled (no Pro token in the lab).
Verified2026-10-19 by Sn0wAlice on 22.04, Proxmox VM, Ubuntu 22.04 cloud image, kernel 5.15.0-198-generic. Fails on stock (qemu-guest-agent from universe, not attached to Ubuntu Pro); passes with a shimmed pro security-status reporting esm-apps enabled (no Pro token in the lab).
Verified2026-10-19 by Sn0wAlice on 24.04, Proxmox VM, Ubuntu 24.04 cloud image, kernel 6.8.0-147-generic. Fails on stock (qemu-guest-agent from universe, not attached to Ubuntu Pro); passes with a shimmed pro security-status reporting esm-apps enabled (no Pro token in the lab).
Verified2026-10-19 by Sn0wAlice on 26.04, Proxmox VM, Ubuntu 26.04 cloud image, kernel 7.0.0-38-generic. Fails on stock (qemu-guest-agent from universe, not attached to Ubuntu Pro); passes with a shimmed pro security-status reporting esm-apps enabled (no Pro token in the lab).
Introduced inv0.1.0
Created, updated2026-10-19, 2026-10-19
Translationsfr