API token disclosure via plaintext job configuration
Published Sep 21, 2022 · Updated May 28, 2025
Plaintext token storage in Jenkins CONS3RT Plugin 1.0.0 and earlier allows local users to read the CONS3RT API token. The plugin serializes the token without encryption into each job config.xml file on the Jenkins controller. Exploitation requires controller filesystem access and exposes the configured token without altering jobs or interrupting service.
Summary
What happened
Plaintext token storage in Jenkins CONS3RT Plugin 1.0.0 and earlier allows local users to read the CONS3RT API token. The plugin serializes the token without encryption into each job config.xml file on the Jenkins controller. Exploitation requires controller filesystem access and exposes the configured token without altering jobs or interrupting service.
The record
- CVE
- CVE-2022-41255
- Published
- Sep 21, 2022
- Updated
- May 28, 2025
- Vendor
- Jenkins Project
- Product
- CONS3RT Plugin
- Classifications
- CWE-256, CWE-522, T1552.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 21, 2022CVE publishedPublication date reported by the CVE source.
- May 28, 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 <=1.0.0
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