Approved changes feed: RSS · Atom

cpe:2.3:a:pagerduty:rundeck:*:*:*:*:enterprise:*:*:*

part: a version: * update: *

VendorPagerduty (205c1399-9b0c-5586-92d6-44ae61e0d5cc)
ProductRundeck (2b9a7825-ff01-59e6-85ce-27254349d01f)
Edition*
Language*
Software editionenterprise
Target software*
Target hardware*
Other*
NotesImported from purl2cpe mapping

PURL mappings

PURLSourceLast updated
pkg:github/rundeck/rundeck purl2cpe 2026-06-01 10:13:25.531289
pkg:maven/org.rundeck/rundeck purl2cpe 2026-06-01 10:13:25.531290

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2022-29186 vulnerable 2026-06-08 05:42:47.296004 Use of Hard-coded Cryptographic Key in rundeck/rundeck, rundeckpro/enterprise
CRITICAL (9.1)
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 id_rsa.pub public key of the keypair was copied to authorized_keys 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 id_rsa.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 authorized_keys files and, if you have copied the public key file included in the docker image, remove it from any authorized_keys files.
Published: 2022-05-20T20:20:11.000Z
Updated: 2025-04-23T18:23:50.364Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2021-39132 vulnerable 2026-06-08 05:33:48.922464 YAML deserialization can run untrusted code
HIGH (8.8)
Rundeck is an open source automation service with a web console, command line tools and a WebAPI. Prior to version 3.3.14 and version 3.4.3, an authorized user can upload a zip-format plugin with a crafted plugin.yaml, or a crafted aclpolicy yaml file, or upload an untrusted project archive with a crafted aclpolicy yaml file, that can cause the server to run untrusted code on Rundeck Community or Enterprise Edition. An authenticated user can make a POST request, that can cause the server to run untrusted code on Rundeck Enterprise Edition. The zip-format plugin issues requires authentication and authorization to these access levels, and affects all Rundeck editions:`admin` level access to the `system` resource type. The ACL Policy yaml file upload issues requires authentication and authorization to these access levels, and affects all Rundeck editions: `create` `update` or `admin` level access to a `project_acl` resource, and/or`create` `update` or `admin` level access to the `system_acl` resource. The unauthorized POST request requires authentication, but no specific authorization, and affects Rundeck Enterprise only. Patches are available in versions 3.4.3, 3.3.14
Published: 2021-08-30T19:35:10.000Z
Updated: 2024-08-04T01:58:17.769Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.