CVE-2018-5223
Last modified
CVE-2018-5223 is a vulnerability of currently unknown severity. Fisheye and Crucible 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 add a repository in Fisheye or Crucible can execute code of their choice on systems that run a vulnerable version of Fisheye or Crucible on the Windows operating system. EPSS estimates a 2.20% chance of exploitation in the next 30 days.
Description
Fisheye and Crucible 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 add a repository in Fisheye or Crucible can execute code of their choice on systems that run a vulnerable version of Fisheye or Crucible on the Windows operating system. All versions of Fisheye and Crucible before 4.4.6 (the fixed version for 4.4.x) and from 4.5.0 before 4.5.3 (the fixed version for 4.5.x) are affected by this vulnerability.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Atlassian | Fisheye | >= 4.4.0, < 4.4.6 |
| Atlassian | Fisheye | >= 4.5.0, < 4.5.3 |
| Atlassian | Crucible | >= 4.4.0, < 4.4.6 |
| Atlassian | Crucible | >= 4.5.0, < 4.5.3 |
References
- http://www.securityfocus.com/bid/103665Third Party Advisory, VDB Entry
- https://confluence.atlassian.com/x/Zi5sOVendor Advisory
- https://confluence.atlassian.com/x/aS5sOVendor Advisory
- https://jira.atlassian.com/browse/CRUC-8181Patch, Vendor Advisory
- https://jira.atlassian.com/browse/FE-7014Patch, Vendor Advisory
- http://www.securityfocus.com/bid/103665Third Party Advisory, VDB Entry
- https://confluence.atlassian.com/x/Zi5sOVendor Advisory
- https://confluence.atlassian.com/x/aS5sOVendor Advisory
- https://jira.atlassian.com/browse/CRUC-8181Patch, Vendor Advisory
- https://jira.atlassian.com/browse/FE-7014Patch, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2018-5223?
How severe is CVE-2018-5223?
How do I fix CVE-2018-5223?
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-5216Radiant CMS 1.1.4 has XSS via crafted Markdown input in the …
- 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-5224Bamboo did not correctly check if a configured Mercurial rep…
- 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…
Are you affected by CVE-2018-5223?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
