CVE-2023-39153: CSRF vulnerability in GitLab Authentication Plugin
Summary
CVE-2023-39153: CSRF vulnerability in GitLab Authentication Plugin. Affects org.jenkins-ci.plugins:gitlab-oauth versions < 1.18. Fixed in 1.18. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The GitLab Authentication Plugin is a Maven package that provides OAuth authentication for Jenkins users using GitLab as the identity provider. It allows users to log in to Jenkins using their GitLab credentials. The plugin version 1.17.1 and earlier are affected by a CSRF vulnerability in its OAuth flow.
Vulnerability Detail
The vulnerability in the GitLab Authentication Plugin arises from the absence of a state parameter in its OAuth flow. The state parameter is a unique and non-guessable value associated with each authentication request. This omission allows attackers to trick users into logging in to the attacker's account. The vulnerability has a CVSS score of 5.4, indicating a moderate severity level. The issue has been identified and fixed in version 1.18 of the plugin, which implements the state parameter in its OAuth flow.
How To Fix
Latest published version: 1.30 as of 23 Oct 2026
Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
1.18
This is the first release that contains the fix.
Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
There is no specific workaround mentioned for this vulnerability. Users are advised to upgrade to the fixed version of the plugin.
Conclusion
The GitLab Authentication Plugin version 1.17.1 and earlier are affected by a CSRF vulnerability in its OAuth flow. This vulnerability allows attackers to trick users into logging in to their accounts. Users should upgrade to version 1.18 or later to fix the vulnerability. For further support on vulnerability remediation, contact DevNack.com.
See every vulnerability recorded for org.jenkins-ci.plugins:gitlab-oauth →
FAQ
The vulnerability allows attackers to trick users into logging in to their accounts, potentially leading to unauthorized access and misuse of sensitive information.
You can use Vulert Playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities without requiring access to the code or installation.
The CVSS score of this vulnerability is 5.4, indicating a moderate severity level.
Yes, the vulnerability has been fixed in version 1.18 of the GitLab Authentication Plugin. Users are advised to upgrade to this version or later.
There are no specific workarounds mentioned for this vulnerability. Upgrading to the fixed version is the recommended solution.
References
Related vulnerabilities
Recent vulnerabilities recorded for org.jenkins-ci.plugins:gitlab-oauth.
