Private-key disclosure via plaintext agent configuration
Published Apr 12, 2022 · Updated Oct 15, 2024
Plaintext key storage in Jenkins Project Google Compute Engine Plugin 4.3.8 and earlier allows remote authenticated users to read private keys. The plugin serializes cloud-agent private keys directly into controller-side config.xml files instead of encrypting their stored values. Agent/Extended Read permission exposes the files through Jenkins, while controller file-system access provides a local path to the same keys.
Summary
What happened
Plaintext key storage in Jenkins Project Google Compute Engine Plugin 4.3.8 and earlier allows remote authenticated users to read private keys. The plugin serializes cloud-agent private keys directly into controller-side config.xml files instead of encrypting their stored values. Agent/Extended Read permission exposes the files through Jenkins, while controller file-system access provides a local path to the same keys.
The record
- CVE
- CVE-2022-29052
- Published
- Apr 12, 2022
- Updated
- Oct 15, 2024
- Vendor
- Jenkins Project
- Product
- Google Compute Engine Plugin
- Classifications
- CWE-522, CWE-256, T1552.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 12, 2022CVE publishedPublication date reported by the CVE source.
- Oct 15, 2024Record 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=unspecified <=4.3.8
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.
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