CVE-2019-10333 json
Jenkins ElectricFlow Plugin Missing permission checks
published 7y ago modified 4mo ago also GHSA-m8f2-9282-x38v , EUVD-2022-4521
- cvss
- 4.3
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 71%
- public exploits
- 0
- none known
Summary
Missing permission checks in Jenkins ElectricFlow Plugin 1.1.5 and earlier in various HTTP endpoints allowed users with Overall/Read access to obtain information about the Jenkins ElectricFlow Plugin configuration and configuration of connected ElectricFlow instances.
Patch / fix
- maven org.jenkins-ci.plugins:electricflow 1.1.7
Is CVE-2019-10333 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
1.33% chance of exploitation in the next 30 days, higher than 71% 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.0 | 4.3 | CVSS:3.0/AV:N/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:electricflow | <1.1.7 |
1.1.7 |
Affected products
- Jenkins project Jenkins ElectricFlow Plugin
Classification
- Weakness
-
- CWE-862 Missing Authorization
References
-
openwall.com
/lists/oss-security/2019/06/11/1
mailing-list, web, third-party-advisory
-
securityfocus.com
/bid/108747
vdb-entry, third-party-advisory
- jenkins.io /security/advisory/2019-06-11/#SECURITY-1410%20%282%29
-
nvd.nist.gov
/vuln/detail/CVE-2019-10333
advisory
-
jenkins.io
/security/advisory/2019-06-11/#SECURITY-1410%20(2)
web
-
web.archive.org
/web/20200227033720/http://www.securityfocus.com/bid/108747
web
Sources
- CVE List CVE-2019-10333
- GitHub Advisory GHSA-m8f2-9282-x38v
- NVD CVE-2019-10333
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.