Jenkins Configuration as Code Plugin 1.55 and earlier used a non-constant time comparison function when validating an authentication token allowing attackers to use statistical methods to obtain a valid authentication token.
Product
Jenkins Project Jenkins Configuration as Code Plugin vulnerabilities
7 published CVES affecting Jenkins Project Jenkins Configuration as Code Plugin, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 7
- Critical
- 0
- High
- 0
- Medium
- 6
- Low
- 1
- Unscored
- 0
- CISA KEV
- 0
Latest Jenkins Project Jenkins Configuration as Code Plugin CVEs
Newest publication first
-
MediumCVSS 5.3 EPSS 1.2% PoC
-
MediumCVSS 5.5 EPSS 0.38%
Due to an incomplete fix of CVE-2019-10343, Jenkins Configuration as Code Plugin 1.26 and earlier did not properly apply masking to some values expected to be hidden when logging the configuration being applied.
-
CVE-2019-10362 Improper Encoding or Escaping of Output in Jenkins Configuration as Code Plugin
PublishedMediumCVSS 5.4 EPSS 0.74%Jenkins Configuration as Code Plugin 1.24 and earlier did not escape values resulting in variable interpolation during configuration import when exporting, allowing attackers with permission to change Jenkins system configuration to obtain the values of environment variables.
-
MediumCVSS 5.5 EPSS 0.33%
Jenkins Configuration as Code Plugin 1.20 and earlier did not treat the proxy password as a secret to be masked when logging or encrypted for export.
-
MediumCVSS 4.9 EPSS 0.61%
Jenkins Configuration as Code Plugin 1.24 and earlier did not reliably identify sensitive values expected to be exported in their encrypted form.
-
MediumCVSS 4.3 EPSS 0.69%
Missing permission checks in Jenkins Configuration as Code Plugin 1.24 and earlier in various HTTP endpoints allowed users with Overall/Read access to access the generated schema and documentation for this plugin containing detailed information about installed plugins.
-
LowCVSS 3.3 EPSS 0.37%
Jenkins Configuration as Code Plugin 1.24 and earlier did not properly apply masking to values expected to be hidden when logging the configuration being applied.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.