Security readout for executives and security teams
Plain-English summary
Atlassian Fisheye and Crucible had an authorization gap that could reveal whether a repository exists and expose review coverage statistics to someone without repository access. This is an information disclosure issue, not described as code execution or full repository access in the supplied sources.
Executive priority
Prioritize remediation where Fisheye or Crucible is externally reachable or hosts sensitive private repositories. The issue appears narrower than compromise-level vulnerabilities, but it can leak information useful for reconnaissance.
Technical view
The affected REST resource `/rest/review-coverage-chart/1.0/data/<repository_name>/.json` lacked a permissions check before Fisheye and Crucible 4.5.1 and 4.6.0. Remote attackers without access to a repository could infer its existence and read review coverage statistics. The CVE maps to CWE-284.
Likely exposure
Organizations running Atlassian Fisheye and Crucible versions prior to 4.5.1 or 4.6.0 are potentially exposed, especially if the application is reachable by untrusted users or the internet.
Exploitation context
The supplied sources do not indicate active exploitation, and the CVE is not marked as CISA KEV. Exploitation impact is limited in the sources to unauthorized repository existence discovery and review coverage statistics disclosure.
Researcher notes
Evidence is limited to the CVE description and Atlassian issue references. No CVSS vector, exploit evidence, or detailed advisory text is present in the supplied bundle, so impact assessment should remain bounded to unauthorized metadata and statistics disclosure.
Mitigation direction
- Upgrade Fisheye and Crucible to 4.5.1, 4.6.0, or a later vendor-supported version.
- Review Atlassian FE-6996 and CRUC-8163 for vendor-specific fix details.
- Restrict Fisheye and Crucible access to trusted networks and authenticated users where feasible.
- Treat exposed repository names and coverage metrics as potentially disclosed before remediation.
Validation and detection
- Inventory all Fisheye and Crucible deployments and record exact versions.
- Confirm no deployment is running a version earlier than 4.5.1 or 4.6.0.
- Review access logs for unexpected requests to the review coverage chart REST resource.
- Verify repository authorization behavior after applying the vendor-fixed version.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2017-18035 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
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://jira.atlassian.com/browse/FE-6996CVE reference · x_refsource_CONFIRM
- https://jira.atlassian.com/browse/CRUC-8163CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.