Vulnerability Monitor

The vendors, products, and vulnerabilities you care about

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.


Security Impact Summary

This vulnerability carries a MEDIUM severity rating with a CVSS v3.1 score of 6.3, indicating it can be exploited remotely over the network with relatively low complexity without requiring user interaction requiring only low-level privileges . The vulnerability impacts limited data confidentiality, limited integrity, and limited availability for affected systems. Impacting 1 product from jenkins organizations running these solutions should prioritize assessment and patching.

Historical Context

First disclosed in 2017, this vulnerability was reported during a period defined by widespread IoT adoption challenges, mobile security concerns, and the emergence of advanced persistent threat (APT) techniques. Contemporary mitigation strategies focused on secure development practices and third-party component vetting.


Published

2017-10-05T01:29:03.743

Last Modified

2025-04-20T01:37:25.860

Status

Deferred

Source

[email protected]

Severity

CVSSv3.0: 6.3 (MEDIUM)

CVSSv2 Vector

AV:N/AC:M/Au:N/C:P/I:P/A:P

  • Access Vector: NETWORK
  • Access Complexity: MEDIUM
  • Authentication: NONE
  • Confidentiality Impact: PARTIAL
  • Integrity Impact: PARTIAL
  • Availability Impact: PARTIAL
Exploitability Score

8.6

Impact Score

6.4

Weaknesses
  • Type: Primary
    CWE-352

Affected Vendors & Products
Type Vendor Product Version/Range Vulnerable?
Application jenkins github_branch_source 0.1 Yes
Application jenkins github_branch_source 0.1 Yes
Application jenkins github_branch_source 0.1 Yes
Application jenkins github_branch_source 0.1 Yes
Application jenkins github_branch_source 1.0 Yes
Application jenkins github_branch_source 1.1 Yes
Application jenkins github_branch_source 1.2 Yes
Application jenkins github_branch_source 1.3 Yes
Application jenkins github_branch_source 1.4 Yes
Application jenkins github_branch_source 1.4 Yes
Application jenkins github_branch_source 1.5 Yes
Application jenkins github_branch_source 1.6 Yes
Application jenkins github_branch_source 1.7 Yes
Application jenkins github_branch_source 1.8 Yes
Application jenkins github_branch_source 1.8.1 Yes
Application jenkins github_branch_source 1.9 Yes
Application jenkins github_branch_source 1.10 Yes
Application jenkins github_branch_source 2.0.0 Yes
Application jenkins github_branch_source 2.0.0 Yes
Application jenkins github_branch_source 2.0.0 Yes
Application jenkins github_branch_source 2.0.1 Yes
Application jenkins github_branch_source 2.0.1 Yes
Application jenkins github_branch_source 2.0.1 Yes
Application jenkins github_branch_source 2.0.1 Yes
Application jenkins github_branch_source 2.0.1 Yes
Application jenkins github_branch_source 2.0.1 Yes
Application jenkins github_branch_source 2.0.1 Yes
Application jenkins github_branch_source 2.0.2 Yes
Application jenkins github_branch_source 2.0.3 Yes
Application jenkins github_branch_source 2.0.4 Yes
Application jenkins github_branch_source 2.0.4 Yes
Application jenkins github_branch_source 2.0.5 Yes
Application jenkins github_branch_source 2.0.6 Yes
Application jenkins github_branch_source 2.0.7 Yes
Application jenkins github_branch_source 2.2.0 Yes
Application jenkins github_branch_source 2.2.0 Yes
Application jenkins github_branch_source 2.2.0 Yes
Application jenkins github_branch_source 2.2.0 Yes
Application jenkins github_branch_source 2.2.0 Yes

References

How SecUtils Interprets This CVE

SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For jenkins's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.