# CVE-2017-7517: Information disclosure in Hawkular Metrics

> Attackers can access metrics from deleted OpenShift projects by recreating them with the same name, exposing sensitive historical data.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Oct 2022
- **Updated:** 13 May 2025
- **Also known as:** GHSA-946m-r2cc-x4j3

## What is CVE-2017-7517?

CVE-2017-7517 is a low-severity vulnerability in Redhat Openshift, published on 17 Oct 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

An input validation vulnerability exists in Openshift Enterprise due to a 1:1 mapping of tenants in Hawkular Metrics and projects/namespaces in OpenShift. If a user creates a project called "MyProject", and then later deletes it another user can then create a project called "MyProject" and access the metrics stored from the original "MyProject" instance.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Redhat Openshift.

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

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

## Is CVE-2017-7517 being exploited?

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

## Other vulnerabilities in Redhat Openshift

- [CVE-2014-3496](https://insights.sbomify.com/CVE-2014-3496/): Command injection in n/a (critical 10.0)
- [CVE-2014-0234](https://insights.sbomify.com/CVE-2014-0234/): Hardcoded credentials in Red Hat OpenShift Enterprise (critical 9.8)
- [CVE-2013-2060](https://insights.sbomify.com/CVE-2013-2060/): Command injection in OpenShift Origin (critical 9.8)
- [CVE-2013-4561](https://insights.sbomify.com/CVE-2013-4561/): Path traversal in openshift-origin-msg-node-mcollective (critical 9.1)
- [CVE-2014-0163](https://insights.sbomify.com/CVE-2014-0163/): Command injection in Openshift (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-7517 is a low-severity vulnerability in Redhat Openshift, published on 17 Oct 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-7517 in the wild and no public exploit code.

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

## Sources

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

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