CVE-2018-5223 json
Fisheye and Crucible did not correctly check if a configured Mercurial repository URI contained values that the Windows operating system ma…
published 2018-03-29 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-17006
- cvss
- 7.2
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.1%
- EPSS 2.1% chance of exploitation in 30 days, percentile 81%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Atlassian Fisheye and Crucible 4.4.6, 4.5.3
- jira.atlassian.com/browse/CRUC-8181 advisory
- jira.atlassian.com/browse/FE-7014 advisory
Exploit prediction
2.08% chance of exploitation in the next 30 days, higher than 81% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.2 | CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.5 | AV:N/AC:L/Au:S/C:P/I:P/A:P |
Affected products
- Atlassian Fisheye and Crucible
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
jira.atlassian.com
/browse/CRUC-8181
patch, vendor-advisory
-
jira.atlassian.com
/browse/FE-7014
patch, vendor-advisory
-
confluence.atlassian.com
/x/aS5sO
vendor-advisory
-
confluence.atlassian.com
/x/Zi5sO
vendor-advisory
-
securityfocus.com
/bid/103665
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2018-5223
- NVD CVE-2018-5223
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.