Unauthorized SSH access via pre-generated private key
Published May 20, 2022 · Updated Apr 23, 2025
Hard-coded SSH keys in PagerDuty Rundeck Docker images 4.0 and earlier allow remote attackers to access hosts configured with the exposed key. The Ubuntu base-image Dockerfile generated one SSH key pair at build time, so every resulting image exposed the same private credential. Exploitation requires an operator to copy the bundled public key into a remote host's authorized_keys file; access carries that account's privileges.
Summary
What happened
Hard-coded SSH keys in PagerDuty Rundeck Docker images 4.0 and earlier allow remote attackers to access hosts configured with the exposed key. The Ubuntu base-image Dockerfile generated one SSH key pair at build time, so every resulting image exposed the same private credential. Exploitation requires an operator to copy the bundled public key into a remote host's authorized_keys file; access carries that account's privileges.
The record
- CVE
- CVE-2022-29186
- Published
- May 20, 2022
- Updated
- Apr 23, 2025
- Vendor
- PagerDuty
- Product
- Rundeck
- Classifications
- CWE-798, CWE-321, T1078, T1552.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 20, 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.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
Weakness, pattern, technique
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