dbcve.org
Google LoginApplication · Jenkins

CVE-2015-5298

MEDIUM · 6.5 CVSS v3.1 Published 2022-07-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
The Google Login Plugin (versions 1.0 and 1.1) allows malicious anonymous users to authenticate successfully against Jenkins instances that are supposed to be locked down to a particular Google Apps domain through client-side request modification.

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

The Google Login Plugin versions 1.0 and 1.1 fails to properly enforce domain restrictions on the server side, allowing attackers to bypass the intended Google Apps domain lockout through client-side request modification. This enables anonymous or unauthorized users to authenticate to Jenkins instances that should be restricted to a specific domain.

MitigationUpgrade the Google Login Plugin to version 1.2 or later which includes server-side validation of domain restrictions. If immediate patching is not possible, disable the plugin or implement additional authentication controls.

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
Affected:= 1.0= 1.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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. Check if Google Login plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab, or check the plugin directory (typically $JENKINS_HOME/plugins/) for google-login directory
    Affected if The Google Login plugin directory exists in the Jenkins plugins folder
  2. Determine installed version of Google Login plugin
    In Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed tab and locate the Google Login plugin entry to see its version number; alternatively, inspect the plugin's manifest file (META-INF/MANIFEST.MF) inside the google-login.hpi file
    Affected if The version is 1.0 or 1.1
  3. Check if domain restriction is configured
    Navigate to Manage Jenkins > Configure Global Security > Access Control > Google Login Plugin section, or check the Jenkins configuration XML (config.xml) for <useGoogleLogin> and <allowedDomains> elements
    Affected if Domain restrictions are configured (specific domains are set in allowedDomains configuration)
  4. Verify the plugin is enabled for authentication
    Check Jenkins global security configuration (Manage Jenkins > Configure Global Security) to confirm that Google Login is selected as the Security Realm / Access Control mechanism
    Affected if Google Login plugin is set as the active authentication method

You are affected if the Google Login plugin versions 1.0 or 1.1 is installed, domain restrictions are configured, and the plugin is enabled as the authentication method.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade the Google Login Plugin to version 1.2 or later which includes server-side validation of domain restrictions. If immediate patching is not possible, disable the plugin or implement additional authentication controls.

Recommended fix Moderate confidence

Google Login Plugin version 1.2 or later

  1. Navigate to 'Manage Jenkins' > 'Manage Plugins' > 'Installed' tab
  2. Locate the 'Google Login Plugin' in the list
  3. Check the current installed version - if it shows 1.0 or 1.1, an upgrade is required
  4. Go to the 'Available' tab and search for 'Google Login Plugin'
  5. Select the latest available version (version 1.2 or later) and click 'Install'
  6. Restart Jenkins after installation completes
  7. Verify the new version is installed under 'Manage Jenkins' > 'Manage Plugins' > 'Installed'
  8. Test authentication to ensure the domain restriction is properly enforced
Caveat Review plugin documentation for any configuration changes required between versions 1.0/1.1 and 1.2, as minor version upgrades may include configuration adjustments

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

Fix this in Google Login 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 help mitigating

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-2015-5298 — 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-2015-5298 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