Google LoginApplication · Jenkins
CVE-2022-46683
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 · uneditedJenkins Google Login Plugin 1.4 through 1.6 (both inclusive) improperly determines that a redirect URL after login is legitimately pointing to Jenkins.
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 confidenceThe Jenkins Google Login Plugin versions 1.4 through 1.6 contain an open redirect vulnerability where the plugin improperly validates redirect URLs after login. An attacker could craft a malicious link that, after successful Google authentication, redirects users to an attacker-controlled website instead of back to the legitimate Jenkins instance.
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
Google LoginApplication
>= 1.4, < 1.7CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Google Login Plugin versionNavigate to Manage Jenkins > Manage Plugins > Installed tab and locate the Google Login plugin in the list. Note the version number displayed in the Version column.Affected if The version shown is 1.4, 1.5, or 1.6 (versions 1.4 through 1.6 are affected)
-
Verify plugin is installed and activeIn the same Installed plugins list, confirm that Google Login shows as 'Enabled' or 'Active' rather than disabled or with a warning indicator.Affected if The plugin is installed and enabled, and the version falls within the affected range from step 1
-
Confirm Google authentication is configuredNavigate to Manage Jenkins > Configure Global Security > Security Realm section. Verify that 'Google OAuth 2.0' or 'Google Login' is selected as the security realm.Affected if Google Login is set as the active security realm, meaning users would authenticate via Google and could be vulnerable to the redirect manipulation
You are affected if the Google Login Plugin version is 1.4, 1.5, or 1.6 AND the plugin is enabled and configured as the authentication method 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.
dbcve · scoped1.7
Upgrade the Google Login Plugin to version 1.7 or later, which contains proper validation of redirect URLs to ensure they point to the legitimate Jenkins instance.
Google Login Plugin version 1.7 or later
- Navigate to Jenkins dashboard and go to 'Manage Jenkins'
- Click on 'Manage Plugins'
- Select the 'Updates' tab
- Locate 'Google Login Plugin' in the list
- Check the plugin version - if it shows a version before 1.7, select it for update
- Click 'Download now and install after restart' or 'Update' button
- Wait for the plugin to update to version 1.7 or later
- Restart Jenkins if required for the update to take effect
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Google Login
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-46683 — 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-2022-46683 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