Credential exposure via inactive storage converter chain
Published Jun 15, 2022 · Updated Apr 23, 2025
Plaintext credential storage in PagerDuty Rundeck 4.2.0 and 4.2.1 allows attackers with backend access to read stored secrets. Rundeck fails to enable the Key Storage converter plugin chain, so key create and update operations bypass its configured encryption layer before persistence. Exposure requires an enabled Storage Converter plugin and credentials created or overwritten while an affected release is running.
Summary
What happened
Plaintext credential storage in PagerDuty Rundeck 4.2.0 and 4.2.1 allows attackers with backend access to read stored secrets. Rundeck fails to enable the Key Storage converter plugin chain, so key create and update operations bypass its configured encryption layer before persistence. Exposure requires an enabled Storage Converter plugin and credentials created or overwritten while an affected release is running.
The record
- CVE
- CVE-2022-31044
- Published
- Jun 15, 2022
- Updated
- Apr 23, 2025
- Vendor
- PagerDuty
- Product
- Rundeck
- Classifications
- CWE-256, T1552
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Jun 15, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 4.2.0, < 4.2.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo