CVE-2019-10371 json
Jenkins Gitlab Authentication Plugin vulnerable to Session Fixation
published 7y ago modified 4mo ago also GHSA-682g-c99v-9r2g , EUVD-2022-2746
- cvss
- 7.5
- 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 70%
- public exploits
- 0
- none known
Summary
A session fixation vulnerability in Jenkins Gitlab Authentication Plugin 1.4 and earlier in GitLabSecurityRealm.java allows unauthorized attackers to impersonate another user if they can control the pre-authentication session.
Patch / fix
- maven org.jenkins-ci.plugins:gitlab-oauth 1.5
Is CVE-2019-10371 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.31% chance of exploitation in the next 30 days, higher than 70% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.jenkins-ci.plugins:gitlab-oauth | <1.5 |
1.5 |
Affected products
- Jenkins project Jenkins Gitlab Authentication Plugin
Classification
- Weakness
-
- CWE-384 Session Fixation
References
-
github.com
/jenkinsci/gitlab-oauth-plugin/commit/695ce63fddb3567cf8d87339ddc1fa3b67ae2db8
web
-
jenkins.io
/security/advisory/2019-08-07/#SECURITY-795
web, vendor-advisory
-
openwall.com
/lists/oss-security/2019/08/07/1
mailing-list, web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-10371
advisory
Sources
- CVE List CVE-2019-10371
- GitHub Advisory GHSA-682g-c99v-9r2g
- NVD CVE-2019-10371
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.