cve.bz

CVE-2017-1000091 jenkins github branch source: Cross Site Reference Forgery

6.3 mediumEPSS 0.6%Fix available

Medium (6.3) in jenkins github branch source. EPSS 0.6% estimated probability of exploitation activity in the next 30 days. Fixed in org.jenkins-ci.plugins:github-branch-source 2.2.0-alpha-1.

On this page
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.

Severity

CVSS 3.0

6.3 medium
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
EPSS
0.6% (unchanged from 0.6% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 52nd percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-352 Cross-Site Request Forgery (Cross Site Reference Forgery)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2017-1000091 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2017-1000091?via=ask-ai-copy and https://cve.bz/cve/CVE-2017-1000091?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2017-1000091 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
jenkins:github_branch_source0.1:beta-1
jenkins:github_branch_source0.1:beta-2
jenkins:github_branch_source0.1:beta-3
jenkins:github_branch_source0.1:beta-4
jenkins:github_branch_source1.0
jenkins:github_branch_source1.1
jenkins:github_branch_source1.2
jenkins:github_branch_source1.3
jenkins:github_branch_source1.4
jenkins:github_branch_source1.4:beta-1
jenkins:github_branch_source1.5
jenkins:github_branch_source1.6
jenkins:github_branch_source1.7
jenkins:github_branch_source1.8
jenkins:github_branch_source1.8.1
jenkins:github_branch_source1.9
jenkins:github_branch_source1.10
jenkins:github_branch_source2.0.0
jenkins:github_branch_source2.0.0:beta-1
jenkins:github_branch_source2.0.0:beta-2
jenkins:github_branch_source2.0.1
jenkins:github_branch_source2.0.1:beta-1
jenkins:github_branch_source2.0.1:beta-2
jenkins:github_branch_source2.0.1:beta-3
jenkins:github_branch_source2.0.1:beta-4
jenkins:github_branch_source2.0.1:beta-5
jenkins:github_branch_source2.0.1:beta-6
jenkins:github_branch_source2.0.2
jenkins:github_branch_source2.0.3
jenkins:github_branch_source2.0.4
jenkins:github_branch_source2.0.4:beta-1
jenkins:github_branch_source2.0.5
jenkins:github_branch_source2.0.6
jenkins:github_branch_source2.0.7
jenkins:github_branch_source2.2.0:alpha-1
jenkins:github_branch_source2.2.0:alpha-2
jenkins:github_branch_source2.2.0:alpha-3
jenkins:github_branch_source2.2.0:alpha-4
jenkins:github_branch_source2.2.0:beta-1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-w66r-f5gg-gqwmMavenorg.jenkins-ci.plugins:github-branch-source<2.2.0-alpha-12.2.0-alpha-1

Attack patterns (CAPEC)

  • CAPEC-62 Cross Site Request Forgery Likelihood: High · Severity: Very High
  • CAPEC-111 JSON Hijacking (aka JavaScript Hijacking) Likelihood: High · Severity: High
  • CAPEC-462 Cross-Domain Search Timing Severity: Medium
  • CAPEC-467 Cross Site Identification Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON