# CVE-2017-18112: Information disclosure in Fisheye

> Remote attackers can view repository HTTP passwords via a logging information disclosure vulnerability in Atlassian Fisheye.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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:** 5 Aug 2020
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-rcrp-5hwf-f7f2

## What is CVE-2017-18112?

CVE-2017-18112 is a medium-severity vulnerability in Atlassian Fisheye, published on 5 Aug 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Affected versions of Atlassian Fisheye allow remote attackers to view the HTTP password of a repository via an Information Disclosure vulnerability in the logging feature. The affected versions are before version 4.8.3.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Atlassian Fisheye.

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

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

## Is CVE-2017-18112 being exploited?

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

## Other vulnerabilities in Atlassian Fisheye

- [CVE-2017-18090](https://insights.sbomify.com/CVE-2017-18090/): Cross-site scripting in Fisheye (medium 6.1)
- [CVE-2017-9510](https://insights.sbomify.com/CVE-2017-9510/): Cross-site scripting in Atlassian Fisheye (medium 5.4)
- [CVE-2011-4822](https://insights.sbomify.com/CVE-2011-4822/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-18112 is a medium-severity vulnerability in Atlassian Fisheye, published on 5 Aug 2020. 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-18112 in the wild and no public exploit code.

Affected product: Atlassian Fisheye. 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-18112/ (Markdown: https://insights.sbomify.com/CVE-2017-18112/index.md)
```

## Sources

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

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