Sensitive data could be exposed in logs of cloud-init before version 23.1.2. An attacker could use this information to find hashed passwords and possibly escalate their privilege.
Information written to log files can be of a sensitive nature and give valuable guidance to an attacker or expose sensitive user information.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Cloud-init | Canonical | * | 23.1.2 (excluding) |
| Ubuntu_linux | Canonical | 16.04 (including) | 16.04 (including) |
| Ubuntu_linux | Canonical | 18.04 (including) | 18.04 (including) |
| Ubuntu_linux | Canonical | 20.04 (including) | 20.04 (including) |
| Ubuntu_linux | Canonical | 22.04 (including) | 22.04 (including) |
| Ubuntu_linux | Canonical | 22.10 (including) | 22.10 (including) |
| Ubuntu_linux | Canonical | 23.04 (including) | 23.04 (including) |
| Red Hat Enterprise Linux 8 | RedHat | cloud-init-0:23.1.1-10.el8 | * |
| Red Hat Enterprise Linux 9 | RedHat | cloud-init-0:23.1.1-11.el9 | * |
| Cloud-init | Ubuntu | bionic | * |
| Cloud-init | Ubuntu | esm-infra/xenial | * |
| Cloud-init | Ubuntu | focal | * |
| Cloud-init | Ubuntu | jammy | * |
| Cloud-init | Ubuntu | kinetic | * |
| Cloud-init | Ubuntu | lunar | * |
| Cloud-init | Ubuntu | trusty | * |
| Cloud-init | Ubuntu | upstream | * |
| Cloud-init | Ubuntu | xenial | * |
While logging all information may be helpful during development stages, it is important that logging levels be set appropriately before a product ships so that sensitive user data and system information are not accidentally exposed to potential attackers. Different log files may be produced and stored for: