CVE-2018-1000185: Jenkins GitHub Branch Source Plugin vulnerable to Server-Side Request Forgery

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

Jenkins GitHub Branch Source Plugin vulnerable to Server-Side Request Forgery

Technologies: org.jenkins-ci.plugins:github-branch-source (Maven). Vendors: Maven.

Quick answers

Is CVE-2018-1000185 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2018-1000185 being exploited in the wild.
How severe is CVE-2018-1000185?
Low severity, with a CVSS score of 3, published 14 May 2022.
Which products and versions are affected?
org.jenkins-ci.plugins:github-branch-source (Maven) ECOSYSTEM:introduced=0,fixed=2.3.5.
Is there a fix for CVE-2018-1000185?
Yes. org.jenkins-ci.plugins:github-branch-source (Maven): upgrade to 2.3.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2018-1000185?
Check whether you run org.jenkins-ci.plugins:github-branch-source (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:github-branch-source (Maven): upgrade to 2.3.5 or later
    # set org.jenkins-ci.plugins:github-branch-source to 2.3.5 in your pom.xml or build.gradle

Affected products

  • org.jenkins-ci.plugins:github-branch-source (Maven) ECOSYSTEM:introduced=0,fixed=2.3.5

Identifiers

  • CVE-2018-1000185
  • GHSA-9cfq-v2hm-c3xr

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