Jira credential disclosure via plaintext configuration storage
Published Mar 9, 2020 · Updated Aug 4, 2024
Cleartext credential storage in Jenkins Project Zephyr for JIRA Test Management Plugin 1.5 and earlier allows local users to read Jira credentials. The plugin writes the credentials unencrypted to com.thed.zephyr.jenkins.reporter.ZfjReporter.xml in the Jenkins controller configuration. Exploitation requires access to the controller file system and exposes the stored Jira credentials without altering Jenkins data or service availability.
Summary
What happened
Cleartext credential storage in Jenkins Project Zephyr for JIRA Test Management Plugin 1.5 and earlier allows local users to read Jira credentials. The plugin writes the credentials unencrypted to com.thed.zephyr.jenkins.reporter.ZfjReporter.xml in the Jenkins controller configuration. Exploitation requires access to the controller file system and exposes the stored Jira credentials without altering Jenkins data or service availability.
The record
- CVE
- CVE-2020-2154
- Published
- Mar 9, 2020
- Updated
- Aug 4, 2024
- Vendor
- Jenkins Project
- Product
- Zephyr for JIRA Test Management Plugin
- Classifications
- CWE-256, CWE-312, T1552.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 9, 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 <=1.5
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