CVE-2019-10344 json
Missing Authorization in Jenkins Configuration as Code Plugin
published 7y ago modified 4mo ago also GHSA-mqr8-3v8j-46wv , EUVD-2022-4612
- cvss
- 4.3
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 53%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- maven io.jenkins:configuration-as-code 1.25
Is CVE-2019-10344 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 FencerExploit prediction
0.69% chance of exploitation in the next 30 days, higher than 53% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:P/I:N/A:N |
| GitHub | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | io.jenkins:configuration-as-code | <1.25 |
1.25 |
Affected products
- Jenkins project Jenkins Configuration as Code Plugin
Classification
References
-
github.com
/jenkinsci/configuration-as-code-plugin/commit/1c531c1a46fc1da6a82cd728bf66428083d30fef
web
-
jenkins.io
/security/advisory/2019-07-31/#SECURITY-1290
web, vendor-advisory
-
openwall.com
/lists/oss-security/2019/07/31/1
mailing-list, web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-10344
advisory
Sources
- CVE List CVE-2019-10344
- GitHub Advisory GHSA-mqr8-3v8j-46wv
- NVD CVE-2019-10344
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.