CVE-2019-10300 json
Jenkins GitLab Plugin Cross-Site Request Forgery vulnerability
published 7y ago modified 4mo ago also GHSA-j365-62px-vjjv , EUVD-2022-4265
- cvss
- 8.0
- version 3.0, 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
A cross-site request forgery vulnerability in Jenkins GitLab Plugin 1.5.11 and earlier in the GitLabConnectionConfig#doTestConnection form validation method allowed attackers to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.
Patch / fix
Is CVE-2019-10300 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.0 | 8.0 | CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 3.5 | AV:N/AC:M/Au:S/C:P/I:N/A:N |
| GitHub | 3.0 | 8.0 | CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.jenkins-ci.plugins:gitlab-plugin | <1.5.12 |
1.5.12 |
Affected products
- Jenkins project Jenkins GitLab Plugin
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
github.com
/jenkinsci/gitlab-plugin/commit/f028c65539a8892f2d1f738cacc1ea5830adf5d3
web
-
jenkins.io
/security/advisory/2019-04-17/#SECURITY-1357
web, vendor-advisory
-
securityfocus.com
/bid/108045
vdb-entry, third-party-advisory
-
talosintelligence.com
/vulnerability_reports/TALOS-2019-0788
web
-
nvd.nist.gov
/vuln/detail/CVE-2019-10300
advisory
Sources
- CVE List CVE-2019-10300
- GitHub Advisory GHSA-j365-62px-vjjv
- NVD CVE-2019-10300
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.