CVE-2017-1000091

UnknownEPSS 0.64%

Last modified

CVE-2017-1000091 is a vulnerability of currently unknown severity. 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. EPSS estimates a 0.64% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability
0.64%

46.0th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersionsUpdate
JenkinsGithub Branch Source0.1Beta-1
JenkinsGithub Branch Source1.0
JenkinsGithub Branch Source1.1
JenkinsGithub Branch Source1.2
JenkinsGithub Branch Source1.3
JenkinsGithub Branch Source1.4
JenkinsGithub Branch Source1.5
JenkinsGithub Branch Source1.6
JenkinsGithub Branch Source1.7
JenkinsGithub Branch Source1.8
JenkinsGithub Branch Source1.8.1
JenkinsGithub Branch Source1.9
JenkinsGithub Branch Source1.10
JenkinsGithub Branch Source2.0.0
JenkinsGithub Branch Source2.0.1
JenkinsGithub Branch Source2.0.2
JenkinsGithub Branch Source2.0.3
JenkinsGithub Branch Source2.0.4
JenkinsGithub Branch Source2.0.5
JenkinsGithub Branch Source2.0.6
JenkinsGithub Branch Source2.0.7
JenkinsGithub Branch Source2.2.0Alpha-1

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is 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.
How severe is CVE-2017-1000091?
Severity scoring for CVE-2017-1000091 is pending analysis. The EPSS model estimates a 0.64% probability of exploitation in the next 30 days.
How do I fix CVE-2017-1000091?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2017-1000091?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST