Credential disclosure via plaintext global configuration storage
Published Jan 24, 2023 · Updated Apr 2, 2025
Plaintext credential storage in Jenkins GitHub Pull Request Coverage Status Plugin 2.2.0 and earlier allows local users to read secrets. The plugin serializes the GitHub Personal Access Token, Sonar access token, and Sonar password directly into com.github.terma.jenkins.githubprcoveragestatus.Configuration.xml without encryption. Access to the Jenkins controller file system is required, and disclosure compromises the configured GitHub and Sonar credentials.
Summary
What happened
Plaintext credential storage in Jenkins GitHub Pull Request Coverage Status Plugin 2.2.0 and earlier allows local users to read secrets. The plugin serializes the GitHub Personal Access Token, Sonar access token, and Sonar password directly into com.github.terma.jenkins.githubprcoveragestatus.Configuration.xml without encryption. Access to the Jenkins controller file system is required, and disclosure compromises the configured GitHub and Sonar credentials.
The record
- CVE
- CVE-2023-24442
- Published
- Jan 24, 2023
- Updated
- Apr 2, 2025
- Vendor
- Jenkins Project
- Product
- GitHub Pull Request Coverage Status Plugin
- Classifications
- CWE-312, T1552.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 24, 2023CVE publishedPublication date reported by the CVE source.
- Apr 2, 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=unspecified <=2.2.0
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