# CVE-2017-15104: Information Exposure in Heketi

> Local attackers can read plain-text passwords from the world-readable Heketi configuration file, exposing sensitive credentials.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Dec 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-q9vw-wr57-xjv3, GO-2022-0866

## What is CVE-2017-15104?

CVE-2017-15104 is a high-severity vulnerability in Redhat Enterprise Linux, published on 18 Dec 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An access flaw was found in Heketi 5, where the heketi.json configuration file was world readable. An attacker having local access to the Heketi server could read plain-text passwords from the heketi.json file.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor), CWE-552 (Files or Directories Accessible to External Parties)

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

3 open source packages ship an affected version, including github.com/heketi/heketi. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/heketi/heketi` | Go | All versions | 5.0.1 |
| `github.com/heketi/heketi` | Go | All versions | 5.0.1 |
| `github.com/heketi/heketi` | Go | All versions | 5.0.1+incompatible |

Products: Heketi Project Heketi, Redhat Enterprise Linux.

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

Upgrade github.com/heketi/heketi to a fixed version for your release line: 5.0.1 or 5.0.1+incompatible.

## Is CVE-2017-15104 being exploited?

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

## Other vulnerabilities in Redhat Enterprise Linux

- [CVE-2017-15103](https://insights.sbomify.com/CVE-2017-15103/): Heketi Arbitrary Code Execution (high 8.8)
- [CVE-2019-3899](https://insights.sbomify.com/CVE-2019-3899/): Missing authorization in heketi (high 7.3)
- [CVE-2020-10763](https://insights.sbomify.com/CVE-2020-10763/): Heketi logs sensitive information (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-15104 is a high-severity vulnerability in Redhat Enterprise Linux, published on 18 Dec 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-15104 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/heketi/heketi (Go): affected all versions; fixed in 5.0.1
- github.com/heketi/heketi (Go): affected all versions; fixed in 5.0.1
- github.com/heketi/heketi (Go): affected all versions; fixed in 5.0.1+incompatible

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-15104/ (Markdown: https://insights.sbomify.com/CVE-2017-15104/index.md)
```

## Sources

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

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