CVE-2017-1000091
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
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Jenkins | Github Branch Source | 0.1 | Beta-1 |
| Jenkins | Github Branch Source | 1.0 | — |
| Jenkins | Github Branch Source | 1.1 | — |
| Jenkins | Github Branch Source | 1.2 | — |
| Jenkins | Github Branch Source | 1.3 | — |
| Jenkins | Github Branch Source | 1.4 | — |
| Jenkins | Github Branch Source | 1.5 | — |
| Jenkins | Github Branch Source | 1.6 | — |
| Jenkins | Github Branch Source | 1.7 | — |
| Jenkins | Github Branch Source | 1.8 | — |
| Jenkins | Github Branch Source | 1.8.1 | — |
| Jenkins | Github Branch Source | 1.9 | — |
| Jenkins | Github Branch Source | 1.10 | — |
| Jenkins | Github Branch Source | 2.0.0 | — |
| Jenkins | Github Branch Source | 2.0.1 | — |
| Jenkins | Github Branch Source | 2.0.2 | — |
| Jenkins | Github Branch Source | 2.0.3 | — |
| Jenkins | Github Branch Source | 2.0.4 | — |
| Jenkins | Github Branch Source | 2.0.5 | — |
| Jenkins | Github Branch Source | 2.0.6 | — |
| Jenkins | Github Branch Source | 2.0.7 | — |
| Jenkins | Github Branch Source | 2.2.0 | Alpha-1 |
References
- https://jenkins.io/security/advisory/2017-07-10/Vendor Advisory
- https://jenkins.io/security/advisory/2017-07-10/Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-1000091?
How severe is CVE-2017-1000091?
How do I fix CVE-2017-1000091?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2017
- CVE-2017-1000085Subversion Plugin connects to a user-specified Subversion re…
- CVE-2017-1000086The Periodic Backup Plugin did not perform any permission ch…
- CVE-2017-1000087GitHub Branch Source provides a list of applicable credentia…
- CVE-2017-1000088The Sidebar Link plugin allows users able to configure jobs,…
- CVE-2017-1000089Builds in Jenkins are associated with an authentication that…
- CVE-2017-1000090Role-based Authorization Strategy Plugin was not requiring r…
- CVE-2017-1000092Git Plugin connects to a user-specified Git repository as pa…
- CVE-2017-1000093Poll SCM Plugin was not requiring requests to its API be sen…
- CVE-2017-1000094Docker Commons Plugin provides a list of applicable credenti…
- CVE-2017-1000095The default whitelist included the following unsafe entries:…
- CVE-2017-1000096Arbitrary code execution due to incomplete sandbox protectio…
- CVE-2017-1000097On Darwin, user's trust preferences for root certificates we…7.5
Are you affected by CVE-2017-1000091?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
