CVSS 3.0
6.3 mediumCVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:LMedium (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.
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:Lorg.jenkins-ci.plugins:github-branch-source (Maven): fixed in 2.2.0-alpha-1Explain 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.
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| jenkins:github_branch_source | 0.1:beta-1 |
| jenkins:github_branch_source | 0.1:beta-2 |
| jenkins:github_branch_source | 0.1:beta-3 |
| jenkins:github_branch_source | 0.1:beta-4 |
| 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.4:beta-1 |
| 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.0:beta-1 |
| jenkins:github_branch_source | 2.0.0:beta-2 |
| jenkins:github_branch_source | 2.0.1 |
| jenkins:github_branch_source | 2.0.1:beta-1 |
| jenkins:github_branch_source | 2.0.1:beta-2 |
| jenkins:github_branch_source | 2.0.1:beta-3 |
| jenkins:github_branch_source | 2.0.1:beta-4 |
| jenkins:github_branch_source | 2.0.1:beta-5 |
| jenkins:github_branch_source | 2.0.1:beta-6 |
| 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.4:beta-1 |
| 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 |
| jenkins:github_branch_source | 2.2.0:alpha-2 |
| jenkins:github_branch_source | 2.2.0:alpha-3 |
| jenkins:github_branch_source | 2.2.0:alpha-4 |
| jenkins:github_branch_source | 2.2.0:beta-1 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-w66r-f5gg-gqwm | Maven | org.jenkins-ci.plugins:github-branch-source | <2.2.0-alpha-1 | 2.2.0-alpha-1 |
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.