CVE-2022-29186: Use of Hard-coded Cryptographic Key in rundeck/rundeck, rundeckpro/enterprise
Rundeck is an open source automation service with a web console, command line tools and a WebAPI. Rundeck community and rundeck-enterprise docker images contained a pre-generated SSH keypair. If the idrsa.pub public key of the keypair was copied to authorizedkeys files on remote host, those hosts would allow access to anyone with the exposed private credentials. This misconfiguration only impacts Rundeck Docker instances of PagerDuty® Process Automation On Prem (formerly Rundeck) version 4.0 and earlier, not Debian, RPM or .WAR. Additionally, the idrsa.pub file would have to be copied from the Docker image filesystem contents without overwriting it and used to configure SSH access on a host. A patch on Rundeck's main branch has removed the pre-generated SSH key pair, but it does not remove exposed keys that have been configured. To patch, users must run a script on hosts in their environment to search for exposed keys and rotate them. Two workarounds are available: Do not use any pre-existing public key file from the rundeck docker images to allow SSH access by adding it to authorizedkeys files and, if you have copied the public key file included in the docker image, remove it from any authorizedkeys files.
Other sources
Rundeck is an open source automation service with a web console, command line tools and a WebAPI. Rundeck community and rundeck-enterprise docker images contained a pre-generated SSH keypair. If the idrsa.pub public key of the keypair was copied to authorizedkeys files on remote host, those hosts would allow access to anyone with the exposed private credentials. This misconfiguration only impacts Rundeck Docker instances of PagerDuty® Process Automation On Prem (formerly Rundeck) version 4.0 and earlier, not Debian, RPM or .WAR. Additionally, the idrsa.pub file would have to be copied from the Docker image filesystem contents without overwriting it and used to configure SSH access on a host. A patch on Rundeck's main branch has removed the pre-generated SSH key pair, but it does not remove exposed keys that have been configured. To patch, users must run a script on hosts in their environment to search for exposed keys and rotate them. Two workarounds are available: Do not use any pre-existing public key file from the rundeck docker images to allow SSH access by adding it to authorizedkeys files and, if you have copied the public key file included in the docker image, remove it from any authorizedkeys files.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is CVE-2022-29186?
CVE-2022-29186 is a vulnerability in Rundeck, an open source automation service, that resulted in pre-generated SSH keypairs being included in the Rundeck community and rundeck-enterprise docker images.
What is the severity of CVE-2022-29186?
CVE-2022-29186 has a severity rating of 9.8 (critical).
How does CVE-2022-29186 affect Rundeck?
CVE-2022-29186 affects Rundeck versions up to and including 4.1.0 when using the Rundeck community or rundeck-enterprise docker images that contained the pre-generated SSH keypair.
How can I fix CVE-2022-29186?
To fix CVE-2022-29186, it is recommended to update to a version of Rundeck that is not affected by the vulnerability and remove the pre-generated SSH keypair from the affected images.
Are there any additional references for CVE-2022-29186?
Yes, additional references for CVE-2022-29186 can be found at the following links: - [GitHub Commit](https://github.com/rundeck/rundeck/commit/16ef7a70b202492f9fbb54d8af4bb8ea0afa10ad) - [GitHub Security Advisory](https://github.com/rundeck/rundeck/security/advisories/GHSA-qxjx-xr2m-hgqx)