CVE-2018-5223: Atlassian Fisheye and Crucible vulnerability

CVE-2018-5223: Fisheye and Crucible did not correctly check if a configured Mercurial repository URI contained values that...

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.

UnknownCVSS not scoredNot KEV-listedUpdatedSep 16, 2024, 19:56 UTC (UTC+00:00)

Security readout for executives and security teams

This flaw affects Atlassian Fisheye and Crucible on Windows. A user allowed to add repositories could supply a Mercurial repository URI that Windows treats as command arguments, potentially leading to code execution on the server. The main concern is misuse by an insider or compromised account with repository-management permissions. Exposure is limited to vulnerable Atlassian Fisheye or Crucible instances running on Windows, especially where Mercurial support is used and repository-add permissions are broadly delegated. Treat this as high priority for Windows-hosted instances because it can become server-side code execution from a privileged application action. Scope first, then patch or restrict permissions quickly. Mitigation focus: Upgrade Fisheye and Crucible to 4.4.6, 4.5.3, or a later fixed version.; Restrict repository-add permissions to trusted administrators only.; Review Atlassian advisory and Jira entries for product-specific upgrade guidance..

Prepared: Jun 7, 2026, 14:22 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2018-5223 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Mar 29, 2018, 13:00 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

5Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5
https://confluence.atlassian.com/x/aS5sOCVE reference · x_refsource_CONFIRM
https://jira.atlassian.com/browse/CRUC-8181CVE reference · x_refsource_CONFIRM
https://confluence.atlassian.com/x/Zi5sOCVE reference · x_refsource_CONFIRM
https://jira.atlassian.com/browse/FE-7014CVE reference · x_refsource_CONFIRM

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

AtlassianFisheye and Crucibleunspecified, 4.5.0, unspecifiedListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.