# CVE-2017-18035: Missing authorization in Fisheye and Crucible

> Remote attackers can access review coverage statistics for repositories they lack permission to view due to a missing permissions check.

- **Severity:** Medium 4.3 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Feb 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-6fpv-4x2f-7hh2

## What is CVE-2017-18035?

CVE-2017-18035 is a medium-severity missing authorization vulnerability in Atlassian Crucible, published on 2 Feb 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The /rest/review-coverage-chart/1.0/data/<repository_name>/.json resource in Atlassian Fisheye and Crucible before version 4.5.1 and 4.6.0 was missing a permissions check, this allows remote attackers who do not have access to a particular repository to determine its existence and access review coverage statistics for it.

Weakness: CWE-862 (Missing Authorization), CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2017-18035?

It affects 2 products.


Products: Atlassian Crucible, Atlassian Fisheye.

## How do I fix CVE-2017-18035?

No fix has been published for CVE-2017-18035 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-18035 being exploited?

There is no known exploitation of CVE-2017-18035 in the wild and no public exploit code.

## Other vulnerabilities in Atlassian Crucible

- [CVE-2021-43958](https://insights.sbomify.com/CVE-2021-43958/): Security feature bypass in Crucible (critical 9.8)
- [CVE-2017-16861](https://insights.sbomify.com/CVE-2017-16861/): Code injection in Fisheye and Crucible (critical 9.8)
- [CVE-2017-14591](https://insights.sbomify.com/CVE-2017-14591/): Command injection in Fisheye and Crucible (critical 9.0)
- [CVE-2020-4018](https://insights.sbomify.com/CVE-2020-4018/): Cross-site request forgery in Crucible (high 8.8)
- [CVE-2018-13399](https://insights.sbomify.com/CVE-2018-13399/): Privilege escalation in Fisheye and Crucible (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-18035 and fix it if it is affected.

What it is: CVE-2017-18035 is a medium-severity missing authorization vulnerability in Atlassian Crucible, published on 2 Feb 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-18035 in the wild and no public exploit code.

Affected product: Atlassian Crucible. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-18035/ (Markdown: https://insights.sbomify.com/CVE-2017-18035/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-18035
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-18035
- OSV: https://osv.dev/vulnerability/CVE-2017-18035

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-18035/
Summaries are generated and may contain mistakes; the official description above is the record.