{"id":172,"date":"2021-05-03T00:41:18","date_gmt":"2021-05-03T00:41:18","guid":{"rendered":"https:\/\/cpearson.icu\/?p=172"},"modified":"2021-05-03T00:41:19","modified_gmt":"2021-05-03T00:41:19","slug":"cve-2021-3429-cloud-init-exposed-credentials-under-certain-conditions","status":"publish","type":"post","link":"https:\/\/cpearson.icu\/?p=172","title":{"rendered":"CVE-2021-3429 cloud-init exposed credentials under certain conditions"},"content":{"rendered":"\n

Vendor:<\/strong> Canonical
Product: <\/strong>cloud-init
Category: <\/strong>CWE-200 Information Exposure
Version:<\/strong> v21.1 and below
Fixed:<\/strong> v21.1.19
CVE:<\/strong> CVE-2021-3429<\/p>\n\n\n\n

Summary<\/h2>\n\n\n\n

Cloud-init enables engineers to automate operating system configuration, primarily within different cloud environments. Cloud-init can also function as a standalone configuration tool independent of any cloud provider.<\/p>\n\n\n\n

Cloud-init includes an optional configuration module, chpasswd, which sets passwords for accounts on the underlying host system. Administrators can instruct cloud-init to set an administrator-defined password or to generate a random password at runtime. The module runs on the first system boot only (technically, the first boot which cloud-init is aware of) and does not run on subsequent boots.<\/p>\n\n\n\n

The chpassword functionality is controlled by creating or modifying a cloud-init configuration file, located by default in the \/etc\/cloud\/cloud.cfg.d\/<\/code> directory. Cloud-init reads all files in this directory and applies configs in order of file read. For example, a configuration file with the following stanza would set the password “P@ssword!” for account bob:<\/p>\n\n\n\n

chpasswd:\n  accounts: |\n    bob:P@ssword!<\/code><\/pre>\n\n\n\n
To generate a random password at runtime instead of a static password, the ‘R’ or ‘RANDOM’ keywords are used in place of a password value. The following sample configuration creates a random password for bob:<\/p>\n\n\n\n
chpasswd:\n  accounts: |\n    bob:RANDOM<\/code><\/pre>\n\n\n\n
With a random password applied, we must have some way of knowing what it was or the account becomes inaccessible for legitimate use! To solve this problem, cloud-init wrote all randomly generated passwords in cleartext to stderr, which sent them to the console during boot. Administrators could find and retrieve passwords from console output.<\/p>\n\n\n\n
Here’s where the vulnerability popped up: cloud-init’s default logging configuration also redirected stdout and stderr to a world readable log file, \/var\/log\/cloud-init-output.log<\/code> . Any unauthorized, unprivileged user could view the cleartext password for any account which had a random password generated at runtime. <\/p>\n\n\n\n
\"\"
root is file owner, but world has read permission<\/figcaption><\/figure>\n\n\n\n
Grepping the log file for “password” as a non-root user and checking for lines surrounding keyword hits revealed any credentials:<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
With credentials in hand, a malicious user could then move laterally on the local system. Only randomly generated passwords were leaked. Statically assigned passwords were not.<\/p>\n\n\n\n
Patch<\/h2>\n\n\n\n
The change password configuration was updated to write randomly generated passwords to \/dev\/console<\/code> instead of stderr. The change preserves printing passwords to console for administrator access, but without also writing the passwords to disk.<\/p>\n\n\n\n
In addition, access to cloud-init-output.log is now restricted. Unprivileged users now cannot read the file. File permissions are changed on cloud-init upgrade; when you update cloud-init, the \/var\/log\/cloud-init-output.log<\/code> file permissions are modified.<\/p>\n\n\n\n
Misc<\/h2>\n\n\n\n
Previously exposed passwords are partially protected with the permission change to the cloud-init-output.log file. However, if the file is copied anywhere, such as inside a system backup, anyone with access to the backup could potentially read the passwords. <\/p>\n\n\n\n
If your cloud-init chpasswd config sets random passwords and also does not force password change on next login (by setting the ‘expire: false” option), then you really need to review your log file and accounts. In other words, if your chpasswd config looks like this:<\/p>\n\n\n\n
chpasswd:\n  expire: false\n  accounts: |\n    alice:RANDOM\n    bob:RANDOM<\/code><\/pre>\n\n\n\n
\u2026then I highly recommend rotating each credential, or at least check if any leaked credentials grant access.<\/p>\n\n\n\n
Finally, cloud-init is installed by default on some operating systems, including Ubuntu Server. While the vulnerable install base is therefore quite large, if  chpassword functionality isn’t used, then the risk is effectively eliminated. You can’t leak passwords you’re not creating…<\/p>\n\n\n\n
Kudos and thank you to the cloud-init team for promptly addressing the vulnerability and issuing a patch!<\/p>\n\n\n\n
Thanks for reading! John 3:16<\/p>\n\n\n\n
Reference:
https:\/\/ubuntu.com\/security\/CVE-2021-3429<\/a>
https:\/\/bugs.launchpad.net\/cloud-init\/+bug\/1918303<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
Vendor: CanonicalProduct: cloud-initCategory: CWE-200 Information ExposureVersion: v21.1 and belowFixed: v21.1.19CVE: CVE-2021-3429 Summary Cloud-init enables engineers to automate operating system configuration, primarily within different cloud environments. Cloud-init can also function as a standalone configuration tool independent of any cloud provider. Cloud-init includes an optional configuration module, chpasswd, which sets passwords for […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2,6],"tags":[],"class_list":["post-172","post","type-post","status-publish","format-standard","hentry","category-advisory","category-write-up"],"_links":{"self":[{"href":"https:\/\/cpearson.icu\/index.php?rest_route=\/wp\/v2\/posts\/172","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cpearson.icu\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cpearson.icu\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cpearson.icu\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/cpearson.icu\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=172"}],"version-history":[{"count":30,"href":"https:\/\/cpearson.icu\/index.php?rest_route=\/wp\/v2\/posts\/172\/revisions"}],"predecessor-version":[{"id":207,"href":"https:\/\/cpearson.icu\/index.php?rest_route=\/wp\/v2\/posts\/172\/revisions\/207"}],"wp:attachment":[{"href":"https:\/\/cpearson.icu\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=172"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cpearson.icu\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=172"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cpearson.icu\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=172"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}