Skip to content

← Public intelligence

Maven package

org.jenkins-ci.plugins:google-login

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

5 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 7.5MavenPublished

    Jenkins Google Login Plugin non-constant time token comparison

    CVE-2023-41936 · GHSA-g58x-57fv-86jh

    Affected
    • Maven org.jenkins-ci.plugins:google-login <= 1.7
    Fixed in
    1.8· Vendor fix available
    Issue
    Jenkins Google Login Plugin 1.7 and earlier uses a non-constant time comparison function when checking whether the provided and expected token are equal, potentially allowing attackers to use statistical methods to obtain a valid token.

    Recommended action: Upgrade to 1.8 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. Medium, CVSS 5.4MavenPublished

    Jenkins Google Login Plugin Open Redirect vulnerability

    CVE-2022-46683 · GHSA-v93c-cxj5-c398

    Affected
    • Maven org.jenkins-ci.plugins:google-login >= 1.4, < 1.7
    Fixed in
    1.7· Vendor fix available
    Issue
    Jenkins Google Login Plugin 1.4 through 1.6 (both inclusive) improperly determines that a redirect URL after login is legitimately pointing to Jenkins. Google Login Plugin 1.7 only redirects to relative (Jenkins) URLs.

    Recommended action: Upgrade to 1.7 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  3. Medium, CVSS 6.5MavenPublished

    Jenkins Google Login Plugin 1.0 and 1.1 allows anonymous users to authenticate through client-side request modification

    CVE-2015-5298 · GHSA-p487-39h9-hm84

    Affected
    • Maven org.jenkins-ci.plugins:google-login >= 1.0, < 1.2
    Fixed in
    1.2· Vendor fix available
    Issue
    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.

    Recommended action: Upgrade to 1.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  4. Medium, CVSS 5.4MavenPublished

    Jenkins Google Login Plugin Open Redirect vulnerability

    CVE-2018-1000174 · GHSA-j279-cx9m-jv3w

    Affected
    • Maven org.jenkins-ci.plugins:google-login <= 1.3
    Fixed in
    1.3.1· Vendor fix available
    Issue
    An open redirect vulnerability exists in Jenkins Google Login Plugin 1.3 and older in GoogleOAuth2SecurityRealm.java that allows attackers to redirect users to an arbitrary URL after successful login. Google Login Plugin 1.3.1 only performs redirects to relative URLs.

    Recommended action: Upgrade to 1.3.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  5. Medium, CVSS 5.9MavenPublished

    Jenkins Google Login Plugin Session Fixation vulnerability

    CVE-2018-1000173 · GHSA-rp82-xvg3-727c

    Affected
    • Maven org.jenkins-ci.plugins:google-login <= 1.3
    Fixed in
    1.3.1· Vendor fix available
    Issue
    A session fixaction vulnerability exists in Jenkins Google Login Plugin 1.3 and older in GoogleOAuth2SecurityRealm.java that allows unauthorized attackers to impersonate another user if they can control the pre-authentication session. Google Login Plugin 1.3.1 invalidates the previous session during login, and creates a new one.

    Recommended action: Upgrade to 1.3.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →