Pagerduty Rundeck 4.2.1 Enterprise Edition

Submit a proposal Propose CVE/GCVE/GHSA reference

Approved changes feed: RSS · Atom

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

part: a version: 4.2.1 update: *

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

PURL mappings

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

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2022-31044 vulnerable 2026-06-08 05:43:40.053921 Plaintext Storage of Keys and Passwords in Rundeck and PagerDuty Process Automation
HIGH (7.5)
Rundeck is an open source automation service with a web console, command line tools and a WebAPI. The Key Storage converter plugin mechanism was not enabled correctly in Rundeck 4.2.0 and 4.2.1, resulting in use of the encryption layer for Key Storage possibly not working. Any credentials created or overwritten using Rundeck 4.2.0 or 4.2.1 might result in them being written in plaintext to the backend storage. This affects those using any `Storage Converter` plugin. Rundeck 4.3.1 and 4.2.2 have fixed the code and upon upgrade will re-encrypt any plain text values. Version 4.3.0 does not have the vulnerability, but does not include the patch to re-encrypt plain text values if 4.2.0 or 4.2.1 were used. To prevent plaintext credentials from being stored in Rundeck 4.2.0/4.2.1, write access to key storage can be disabled via ACLs. After upgrading to 4.3.1 or later, write access can be restored.
Published: 2022-06-15T19:00:22.000Z
Updated: 2025-04-23T18:14:03.690Z
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.