CVE-2022-46683: Jenkins Google Login Plugin Open Redirect vulnerability

Summary

12/12/2022
Yes i
Moderate
5.4

CVE-2022-46683: Jenkins Google Login Plugin Open Redirect vulnerability. Affects org.jenkins-ci.plugins:google-login versions >= 1.4, < 1.7. Fixed in 1.7. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The Jenkins Google Login Plugin is a Maven package (org.jenkins-ci.plugins:google-login) that provides the functionality to allow users to log in to Jenkins using their Google accounts. It integrates with the Google OAuth 2.0 authentication system to authenticate users and grant them access to Jenkins.

Vulnerability Detail

The Jenkins Google Login Plugin versions 1.4 through 1.6 (inclusive) have an open redirect vulnerability. This vulnerability occurs when the plugin fails to properly validate the redirect URL after login, incorrectly assuming that it points to Jenkins. As a result, an attacker can craft a malicious redirect URL that leads users to a different website or page, potentially tricking them into disclosing sensitive information or performing unintended actions.

How To Fix

Minimum fixed version

1.7

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 known workaround for this vulnerability. It is recommended to upgrade to the fixed version of the plugin.

Conclusion

The Jenkins Google Login Plugin versions 1.4 through 1.6 have an open redirect vulnerability that can be exploited by attackers. Users should upgrade to version 1.7 or later to fix this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for org.jenkins-ci.plugins:google-login →

Share this vulnerability

FAQ

This vulnerability can be exploited by an attacker to redirect users to malicious websites or pages, potentially leading to phishing attacks, information disclosure, or unintended actions.

No, only versions 1.4 through 1.6 (inclusive) of the plugin are affected. Version 1.7 and later have fixed this vulnerability.

No, this vulnerability does not allow for authentication bypass. It only affects the validation of redirect URLs after login.

There is no known public exploit for this vulnerability at the time of this report.

You can use Vulert's 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, using just the pom.xml file.

Related vulnerabilities

Recent vulnerabilities recorded for org.jenkins-ci.plugins:google-login.

How To Fix

Minimum fixed version

1.7

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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback