API key exposure via plaintext job configuration
Published Jan 15, 2020 · Updated Aug 4, 2024
Credential exposure in Jenkins Redgate SQL Change Automation Plugin 2.0.4 and earlier allows remote authenticated users to read a NuGet API key. The plugin writes the key unencrypted into each affected job's config.xml instead of using Jenkins credential encryption. Exploitation requires Extended Read permission or access to the Jenkins controller file system and exposes the key without enabling configuration changes or service interruption.
Summary
What happened
Credential exposure in Jenkins Redgate SQL Change Automation Plugin 2.0.4 and earlier allows remote authenticated users to read a NuGet API key. The plugin writes the key unencrypted into each affected job's config.xml instead of using Jenkins credential encryption. Exploitation requires Extended Read permission or access to the Jenkins controller file system and exposes the key without enabling configuration changes or service interruption.
The record
- CVE
- CVE-2020-2095
- Published
- Jan 15, 2020
- Updated
- Aug 4, 2024
- Vendor
- Jenkins Project
- Product
- Redgate SQL Change Automation Plugin
- Classifications
- CWE-522, T1552.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 15, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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 <=2.0.4
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