CVE-2022-41255 json
API token stored in plain text by Jenkins CONS3RT Plugin
published 4y ago modified 4mo ago also GHSA-fmq9-r4p2-8272 , EUVD-2022-6803
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 57%
- public exploits
- 0
- none known
Summary
Jenkins CONS3RT Plugin 1.0.0 and earlier stores Cons3rt API token unencrypted in job config.xml files on the Jenkins controller where it can be viewed by users with access to the Jenkins controller file system.
Is CVE-2022-41255 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.81% chance of exploitation in the next 30 days, higher than 57% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| GitHub | 3.1 | 3.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.jenkins-ci.plugins:cons3rt | <=1.0.0 |
no fix listed |
Affected products
- Jenkins project Jenkins CONS3RT Plugin
Classification
References
-
jenkins.io
/security/advisory/2022-09-21/#SECURITY-2759
web, vendor-advisory
-
openwall.com
/lists/oss-security/2022/09/21/5
mailing-list, web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-41255
advisory
-
github.com
/jenkinsci/cons3rt-plugin
package
Sources
- CVE List CVE-2022-41255
- GitHub Advisory GHSA-fmq9-r4p2-8272
- NVD CVE-2022-41255
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.