Package "cloud-init"

  cloud-init (25.1.4-0ubuntu0~22.04.1) jammy-security; urgency=medium

  * refresh patches:
    - d/p/revert-usr-lib-systemd-units.patch
  * Upstream snapshot based on 25.1.4.
    List of changes from upstream can be found at
    https://raw.githubusercontent.com/canonical/cloud-init/25.1.4/ChangeLog
    - Bugs fixed in this snapshot:
      + fix: disable cloud-init when non-x86 environments have no DMI-data
        and no strict datasources detected (LP: #2069607) (CVE-2024-6174)

 -- Chad Smith <email address hidden> Tue, 24 Jun 2025 15:15:25 -0600

  cloud-init (23.1.2-0ubuntu0~22.04.1) jammy; urgency=medium

  * SECURITY UPDATE: Make user/vendor data sensitive and remove log permissions
    Because user data and vendor data may contain sensitive information,
    this commit ensures that any user data or vendor data written to
    instance-data.json gets redacted and is only available to root user.

    Also, modify the permissions of cloud-init.log to be 640, so that
    sensitive data leaked to the log isn't world readable.
    Additionally, remove the logging of user data and vendor data to
    cloud-init.log from the Vultr datasource.

    This is based on upstream snapshot of 23.1.2 [(LP: #2013967)]

    - d/cloud-init.postinst: postinst fixes for LP: #2013967
      Redact sensitive keys from world-readable instance-data.json on upgrade.
      Set perms 640 for /var/log/cloud-init.log on pkg upgrade.
      Redact sensitive Vultr messages from /var/log/cloud-init.log
    - (CVE-2023-1786)

 -- James Falcon <email address hidden> Thu, 20 Apr 2023 20:37:40 -0500

  cloud-init (22.2-0ubuntu1~22.04.3) jammy-security; urgency=medium

  * SECURITY UPDATE: schema errors can cause cloud-init to leak
    userdata to system logs
    - d/cloud-init.postinst: redact previously leaked schema errors
      from logs
    - Remove schema errors from log (LP: #1978422)
    - CVE-2022-2084

 -- James Falcon <email address hidden> Tue, 14 Jun 2022 06:31:00 -0500