Token disclosure via plaintext job configuration storage
Published Mar 15, 2022 · Updated Aug 3, 2024
Credential exposure in Jenkins Incapptic Connect Uploader Plugin 1.15 and earlier allows attackers to read personal tokens from job configuration. The plugin serializes each configured personal token as plaintext in the job's config.xml file on the Jenkins controller instead of protecting the credential. Exposure requires Job/ExtendedRead permission for an affected job or read access to the controller file system and is limited to stored-token confidentiality.
Summary
What happened
Credential exposure in Jenkins Incapptic Connect Uploader Plugin 1.15 and earlier allows attackers to read personal tokens from job configuration. The plugin serializes each configured personal token as plaintext in the job's config.xml file on the Jenkins controller instead of protecting the credential. Exposure requires Job/ExtendedRead permission for an affected job or read access to the controller file system and is limited to stored-token confidentiality.
The record
- CVE
- CVE-2022-27218
- Published
- Mar 15, 2022
- Updated
- Aug 3, 2024
- Vendor
- Jenkins Project
- Product
- Jenkins Incapptic Connect Uploader Plugin
- Classifications
- CWE-522, T1552.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 15, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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.15
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