Gitlab Authentication vulnerabilitiesRanked by how likely they are to be used.
Gitlab Authentication is made by Jenkins. We track 4 published vulnerabilities in it, across 64 versions. None of them is on the list of flaws known to be exploited today. If you run Gitlab Authentication, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Gitlab Authentication vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Gitlab Authentication's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Gitlab Authentication flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 1.4%CVE-2020-2228High
Jenkins Gitlab Authentication Plugin 1.5 and earlier does not perform group authorization checks properly, resulting in a privilege escalation vulnerability.
- 1.0%CVE-2022-27206Medium
Jenkins GitLab Authentication Plugin 1.13 and earlier stores the GitLab client secret unencrypted in the global config.xml file on the Jenkins controller where it can be viewed by users with access to the Jenkins...
- 0.7%CVE-2022-25196Medium
Jenkins GitLab Authentication Plugin 1.13 and earlier records the HTTP Referer header as part of the URL query parameters when the authentication process starts, allowing attackers with access to Jenkins to craft a...
- 0.7%CVE-2023-39153Medium
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.
Running Gitlab Authentication? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
Jenkins Gitlab Authentication Plugin 1.5 and earlier does not perform group authorization checks properly, resulting in a privilege escalation vulnerability.
- Matched to
- Gitlab Authentication on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 4 published vulnerabilities listed under the name Gitlab Authentication, across 64 versions.
None of Gitlab Authentication's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Gitlab Authentication. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.