CVE-2017-14590: Atlassian Bamboo vulnerability
Atlassian · Bamboo
Affected: Atlassian Bamboo · Exploitation: possible (1 to 10%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 84% of scored CVEs
Not scored yet. The CVE record carries no CVSS score.
DescriptionCVE.org
Bamboo did not check that the name of a branch in a Mercurial repository contained argument parameters. An attacker who has permission to create a repository in Bamboo, edit an existing plan that has a non-linked Mercurialrepository, create or edit a plan when there is at least one linked Mercurial repository that the attacker has permission to use, or commit to a Mercurial repository used by a Bamboo plan which has branch detection enabled can execute code of their choice on systems that run a vulnerable version of Bamboo Server. Versions of Bamboo starting with 2.7.0 before 6.1.6 (the fixed version for 6.1.x) and from 6.2.0 before 6.2.5 (the fixed version for 6.2.x) are affected by this vulnerability.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- Atlassian · Bamboofrom 2.7.0 before 6.1.6 (the fixed version for 6.1.x); from 6.2.0 before 6.2.5
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Possible (1 to 10%). EPSS between 1% and 10%.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- Atlassian
- Published
- December 2017
CoverageNo articles yet
No CyberSIXT article names CVE-2017-14590 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.