CVE-2018-5224
Last modified
CVE-2018-5224 is a vulnerability of currently unknown severity. Bamboo did not correctly check if a configured Mercurial repository URI contained values that the Windows operating system may consider argument parameters. An attacker who has permission to create a repository in Bamboo, edit an existing plan in Bamboo that has a non-linked Mercurial repository, or create a plan in Bamboo either globally or in a project using Bamboo Specs can can execute code of their choice on systems that run a vulnerable version of Bamboo on the Windows operating system. EPSS estimates a 2.82% chance of exploitation in the next 30 days.
Description
Bamboo did not correctly check if a configured Mercurial repository URI contained values that the Windows operating system may consider argument parameters. An attacker who has permission to create a repository in Bamboo, edit an existing plan in Bamboo that has a non-linked Mercurial repository, or create a plan in Bamboo either globally or in a project using Bamboo Specs can can execute code of their choice on systems that run a vulnerable version of Bamboo on the Windows operating system. All versions of Bamboo starting with 2.7.0 before 6.3.3 (the fixed version for 6.3.x) and from version 6.4.0 before 6.4.1 (the fixed version for 6.4.x) running on the Windows operating system are affected by this vulnerability.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Atlassian | Bamboo | >= 2.7.0, < 6.3.3 |
| Atlassian | Bamboo | >= 6.4.0, < 6.4.1 |
References
- http://www.securityfocus.com/bid/103653Third Party Advisory, VDB Entry
- https://confluence.atlassian.com/x/PS9sOMitigation, Vendor Advisory
- https://jira.atlassian.com/browse/BAM-19743Vendor Advisory
- http://www.securityfocus.com/bid/103653Third Party Advisory, VDB Entry
- https://confluence.atlassian.com/x/PS9sOMitigation, Vendor Advisory
- https://jira.atlassian.com/browse/BAM-19743Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2018-5224?
How severe is CVE-2018-5224?
How do I fix CVE-2018-5224?
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 2018
- CVE-2018-5217In K7 Antivirus 15.1.0306, the driver file (K7Sentry.sys) al…
- CVE-2018-5218In K7 Antivirus 15.1.0306, the driver file (K7Sentry.sys) al…
- CVE-2018-5219In K7 Antivirus 15.1.0306, the driver file (K7FWHlpr.sys) al…
- CVE-2018-5220In K7 Antivirus 15.1.0306, the driver file (K7Sentry.sys) al…
- CVE-2018-5221Multiple buffer overflows in BarCodeWiz BarCode before 6.7 A…
- CVE-2018-5223Fisheye and Crucible did not correctly check if a configured…
- CVE-2018-5225In browser editing in Atlassian Bitbucket Server from versio…
- CVE-2018-5226There was an argument injection vulnerability in Sourcetree …
- CVE-2018-5227Various administrative application link resources in Atlassi…
- CVE-2018-5228The /browse/~raw resource in Atlassian Fisheye and Crucible …
- CVE-2018-5229The NotificationRepresentationFactoryImpl class in Atlassian…
- CVE-2018-5230The issue collector in Atlassian Jira before version 7.6.6, …
Are you affected by CVE-2018-5224?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
