Gitlab OauthApplication · Jenkins
CVE-2019-10371
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA session fixation vulnerability in Jenkins Gitlab Authentication Plugin 1.4 and earlier allows attackers who control the pre-authentication session cookie to hijack legitimate user sessions after authentication, enabling user impersonation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Gitlab OauthApplication
<= 1.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Gitlab Authentication Plugin installationNavigate to Jenkins Manage Plugins > Installed tab and search for 'Gitlab Authentication' or 'gitlab-oauth' plugin, or use the Jenkins CLI: java -jar jenkins-cli.jar list-plugins | grep -i gitlabAffected if The plugin appears in the installed plugins list
-
Determine installed plugin versionIn the Installed plugins tab, locate the 'Gitlab Authentication' or 'Gitlab OAuth' plugin and note the Version column. Alternatively, check the plugin's pom.xml or manifest if accessible in the Jenkins plugins directoryAffected if The version number is 1.4 or lower
-
Verify Gitlab OAuth authentication is configuredNavigate to Manage Jenkins > Configure Global Security > Security Realm and check if 'Gitlab Authentication Plugin' or 'Gitlab OAuth' is selected as the Security RealmAffected if Gitlab Authentication/OAuth is enabled as the authentication method
-
Check session handling configurationExamine Jenkins configuration files (config.xml) or security realm settings for session management configuration related to Gitlab authenticationAffected if Gitlab OAuth authentication is active and session tokens are not being regenerated post-authentication
User is affected if Gitlab Authentication Plugin version 1.4 or earlier is installed AND Gitlab OAuth authentication is enabled as the security realm in Jenkins.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to Gitlab Authentication Plugin version 1.5 or later which properly invalidates or regenerates session identifiers during the authentication process.
Fix this in Gitlab Oauth
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10371 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-10371 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data