CVE-2017-1000091 Jenkins GitHub Branch Source Plugin vulnerable to Cross-Site Request Forgery

Medium 6.3 Published Updated

Attackers can exploit CSRF to force Jenkins to send credentials to arbitrary servers, potentially capturing sensitive information.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2017-1000091?

CVE-2017-1000091 is a medium-severity vulnerability in n/a, published on 4 Oct 2017. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

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.

Weakness: CWE-352

Which versions are affected by CVE-2017-1000091?

2 open source packages ship an affected version, including org.jenkins-ci.plugins:github-branch-source. It affects 1 product.

PackageAffectedFixed in
org.jenkins-ci.plugins:github-branch-source MavenAll versions2.2.0-alpha-1
org.jenkins-ci.plugins:github-branch-source MavenAll versions2.2.0-alpha-1

Products include Jenkins Github Branch Source.

How do I fix CVE-2017-1000091?

Upgrade org.jenkins-ci.plugins:github-branch-source to 2.2.0-alpha-1 or later.

Is CVE-2017-1000091 being exploited?

There is no known exploitation of CVE-2017-1000091 in the wild and no public exploit code.

Sources

Also known as GHSA-w66r-f5gg-gqwm.

Is CVE-2017-1000091 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free