CVE-2018-1000173: Jenkins Google Login Plugin Session Fixation vulnerability

CVE-2018-1000173 · Severity: low · CVSS 3 · Published 2022-05-14

Jenkins Google Login Plugin Session Fixation vulnerability

Technologies: org.jenkins-ci.plugins:google-login (Maven). Vendors: Maven.

Quick answers

Is CVE-2018-1000173 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2018-1000173 being exploited in the wild.
How severe is CVE-2018-1000173?
Low severity, with a CVSS score of 3, published 14 May 2022.
Which products and versions are affected?
org.jenkins-ci.plugins:google-login (Maven) ECOSYSTEM:introduced=0,fixed=1.3.1.
Is there a fix for CVE-2018-1000173?
Yes. org.jenkins-ci.plugins:google-login (Maven): upgrade to 1.3.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2018-1000173?
Check whether you run org.jenkins-ci.plugins:google-login (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • org.jenkins-ci.plugins:google-login (Maven): upgrade to 1.3.1 or later
    # set org.jenkins-ci.plugins:google-login to 1.3.1 in your pom.xml or build.gradle

Affected products

  • org.jenkins-ci.plugins:google-login (Maven) ECOSYSTEM:introduced=0,fixed=1.3.1

Identifiers

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

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.