CVE-2017-1000091

GitHub Branch Source Plugin connects to a user-specified GitHub API URL (e.g. GitHub Enterprise) as part of form validation and completion (e.g. to verify Scan Credentials are correct). This functionality improperly checked permissions, allowing any user with Overall/Read access to Jenkins to connect to any web server and send credentials with a known ID, thereby possibly capturing them. Additionally, this functionality did not require POST requests be used, thereby allowing the above to be performed without direct access to Jenkins via Cross-Site Request Forgery. An enumeration of credentials IDs in this plugin now requires the permission to have Extended Read permission (when that permission is enabled; otherwise Configure permission) to the job in whose context credentials are being accessed. If no job context exists, Overall/Administer permission is required.

A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones. Typical impact: state-changing actions performed as the victim without their consent.

CVE-2017-1000091 has a CVSS score of 6.3 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.2.0-alpha-1); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2017-1000091? CVE-2017-1000091 is a medium-severity cross-site request forgery (CSRF) vulnerability in org.jenkins-ci.plugins:github-branch-source (maven), affecting versions < 2.2.0-alpha-1. It is fixed in 2.2.0-alpha-1. A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones.
2. How severe is CVE-2017-1000091? CVE-2017-1000091 has a CVSS score of 6.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of org.jenkins-ci.plugins:github-branch-source are affected by CVE-2017-1000091? org.jenkins-ci.plugins:github-branch-source (maven) versions < 2.2.0-alpha-1 is affected.
4. Is there a fix for CVE-2017-1000091? Yes. CVE-2017-1000091 is fixed in 2.2.0-alpha-1. Upgrade to this version or later.
5. Is CVE-2017-1000091 exploitable, and should I be worried? Whether CVE-2017-1000091 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2017-1000091 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2017-1000091? Upgrade org.jenkins-ci.plugins:github-branch-source to 2.2.0-alpha-1 or later.