On this page (7 sections)

Ubuntu has published security notice USN-9153-1 for cloud-init, the initialization tool that configures many cloud and virtual machine images at first boot. According to the notice, cloud-init incorrectly handled certain errors when configuring user passwords on systems that have SSSD installed but not configured.

If you run Ubuntu servers or images that use cloud-init, particularly in cloud environments, this is worth a quick review. The public details we have are thin, so this article separates what the notice says from what it leaves out.

What the notice says

Ubuntu's notice states that cloud-init incorrectly handled certain errors when configuring user passwords on systems with SSSD installed but not configured. It adds that an attacker could possibly use this issue to access affected user accounts without a password, resulting in unauthorized access.

The wording is cautious: an attacker could "possibly" abuse it. The notice summary available to us does not describe how an attacker would reach the condition, and we are not going to speculate about it.

What we do not know yet

Only one publisher, Ubuntu itself, covers this so far, and the material we have is a short summary. The following details were not available to us, so check the full notice before relying on any of them:

  • A CVE identifier or CVSS score for the issue.
  • Which Ubuntu releases are affected.
  • Whether fixed package versions exist, and what they are.
  • Whether the flaw is being exploited in the wild.
  • Whether other distributions that ship cloud-init are affected.
Severity is unknown from the available research. Treat the issue as one that could possibly allow access to user accounts without a password, and verify the scope, affected releases and fixed versions on the full Ubuntu notice page.

The weakness in plain terms

cloud-init runs early in a machine's life and applies settings such as users and passwords. SSSD is a service that connects Linux systems to central identity providers. The notice describes a case where SSSD is installed but not configured, and cloud-init does not handle certain errors correctly while configuring user passwords. The stated result is possible access to affected accounts without a password.

This is a general class of problem: an error during a security-sensitive setup step that is not handled safely. The notice does not explain the exact mechanism, so we do not describe one here.

Who is realistically exposed

Based only on the notice, the systems to look at are those that match its stated condition:

  • Ubuntu systems that use cloud-init to configure user passwords.
  • Systems where SSSD packages are installed but SSSD is not configured.

The notice summary does not say whether systems without SSSD, or systems that do not use cloud-init for passwords, are affected. Confirm against the full advisory rather than assuming you are safe.

How to check your systems

These are read-only checks using standard Ubuntu tools. First, see which cloud-init version is installed and which version the Ubuntu archive offers. Run this on each Ubuntu host:

Show installed and candidate cloud-init versions (Ubuntu)Shell
apt-cache policy cloud-init

Compare the installed version with the fixed version, if any, that the Ubuntu notice lists for your release. Next, check whether SSSD packages are installed. If the command prints nothing, none are installed:

Check whether SSSD packages are installed (Ubuntu)Shell
dpkg -l | grep -i sssd

If SSSD is installed, check whether it has been configured on that host. The notice's condition is SSSD installed but not configured, so a host in that state matches the scenario worth reviewing.

What to do now

  1. Open the full USN-9153-1 page and note the affected releases and any fixed cloud-init versions.
  2. Inventory Ubuntu hosts and images that use cloud-init, including templates and autoscaling images.
  3. Run the version and SSSD checks above to see which hosts match the notice's condition.
  4. If the notice lists a fixed cloud-init version for your release, install it and re-run the version check.
  5. If you maintain base images or templates, rebuild them with the fixed package once it is available, so new instances start patched.
  6. Review authentication logs for unexpected logins, as described below.
  7. As general hygiene, audit accounts for empty password fields (see the note below).

Only once the notice lists a fix for your release, update the cloud-init package. Refresh package lists and upgrade only that package, then re-run the version check to confirm the new version:

Caution. Test on a non-production instance first. cloud-init affects first-boot configuration, so a bad change to a template can affect every machine created from it.
Update only the cloud-init package (Ubuntu), once a fix is listed for your releaseShell
sudo apt update && sudo apt install --only-upgrade cloud-init

General hygiene: empty password fields

This audit is general account hygiene and is not tied to the notice's stated mechanism. The notice does not say the flaw produces an empty password field, so this check does not detect or confirm this issue. In /etc/shadow, an empty second field means no password is set. The command needs root and only reads the file:

List accounts with an empty password field (run as root; general hygiene, not specific to…Shell
awk -F: '($2 == "") {print $1}' /etc/shadow

Detection and monitoring

Because exploitation is unconfirmed, focus on spotting unexpected logins. Review authentication logs for successful logins to accounts that should not be used interactively, and for logins from unfamiliar addresses. On Ubuntu, this search of the auth log shows recent accepted logins and opened sessions (run as root, and look for accounts or source addresses you do not recognize):

Show recent successful logins in the auth log (Ubuntu, run as root)Shell
grep -i 'accepted\|session opened' /var/log/auth.log | tail -n 50

You can also keep an eye on the externally visible side of your servers. A scan of your public services, such as Webforta Scan, can help you notice exposed login services you did not intend to publish, and monitoring can alert you to certificate or DNS changes. Neither replaces patching the host itself.

For broader hygiene, see our guides on what to do if a website is hacked and small business website security.

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-9153-1: cloud-init vulnerabilityubuntu.com ·
  • cloud-init
  • Ubuntu
  • USN
  • SSSD
  • cloud