dbcve.org
Gitlab AuthenticationApplication · Jenkins

CVE-2023-39153

MEDIUM · 5.4 CVSS v3.1 Published 2023-07-26
Fix available
A fix is available. Upgrade to after 1.17.1 or later.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
A cross-site request forgery (CSRF) vulnerability in Jenkins GitLab Authentication Plugin 1.17.1 and earlier allows attackers to trick users into logging in to the attacker's account.

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 · high confidence

A CSRF vulnerability in Jenkins GitLab Authentication Plugin 1.17.1 and earlier allows attackers to manipulate the authentication flow, tricking users into logging into the attacker's GitLab account instead of their own. This exploits the lack of proper CSRF token validation during the GitLab OAuth authentication process.

MitigationUpdate Jenkins GitLab Authentication Plugin to a version newer than 1.17.1, which should include proper CSRF token validation in the OAuth authentication callback. Additionally, ensure global Jenkins CSRF protection is enabled.

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 AuthenticationApplication
Affected:<= 1.17.1

CVSS 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
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the GitLab Authentication plugin
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'GitLab Authentication', or run: ls $JENKINS_HOME/plugins/ | grep -i gitlab
    Affected if The plugin is not installed or not present in the plugin directory, then the environment is not affected by this specific vulnerability.
  2. Determine the installed plugin version
    In the Installed plugins tab, find the 'GitLab Authentication' plugin and note the version number displayed in the 'Version' column. Alternatively, inspect the plugin manifest: unzip -p $JENKINS_HOME/plugins/gitlab-authentication.jpi META-INF/MANIFEST.MF | grep -i version
    Affected if You must know the exact version number to proceed with the vulnerability assessment.
  3. Compare the installed version to the affected range
    Compare the version you found in step 2 against the affected range: any version of GitLab Authentication plugin that is 1.17.1 or lower is vulnerable
    Affected if If the installed version is 1.17.1 or any earlier version (for example 1.17.0, 1.16.0, 1.15.0), then the environment is affected by CVE-2023-39153.
  4. Verify the plugin is actively used for authentication
    Navigate to Manage Jenkins > Configure Global Security > Security Realm and confirm that 'GitLab Authentication' is selected as the security realm
    Affected if If the plugin is installed but not configured as the active authentication method, the practical impact of this CSRF vulnerability is reduced, though the vulnerable version still exists.

The environment is affected by CVE-2023-39153 if the GitLab Authentication plugin is installed and its version is 1.17.1 or earlier.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 1.17.1
Interim mitigation

Update Jenkins GitLab Authentication Plugin to a version newer than 1.17.1, which should include proper CSRF token validation in the OAuth authentication callback. Additionally, ensure global Jenkins CSRF protection is enabled.

Recommended fix High confidence

GitLab Authentication Plugin version 1.17.2 or later

  1. Navigate to Jenkins dashboard
  2. Go to Manage Jenkins > Manage Plugins
  3. Select the 'Installed' tab
  4. Find 'GitLab Authentication' plugin in the list
  5. If version 1.17.1 or earlier is installed, click 'Update now' to install the latest version
  6. Restart Jenkins if required to complete the update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Gitlab Authentication Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-39153 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-39153 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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