# CVE-2018-15534: Information disclosure in n/a

> Unauthenticated attackers can access sensitive user credentials and hashes by requesting a specific XML file on the re_porter web interface.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Aug 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-f4c4-x5r3-jc4r

## What is CVE-2018-15534?

CVE-2018-15534 is a critical vulnerability in n/a, published on 21 Aug 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Geutebrueck re_porter 16 before 7.8.974.20 has a possibility of unauthenticated access to sensitive information including usernames and hashes via a direct request for /statistics/gscsetup.xml on TCP port 12003.

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

## Which versions are affected by CVE-2018-15534?

It affects 1 product.


Products: Geutebrueck Re Porter 16 Firmware.

## How do I fix CVE-2018-15534?

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

## Is CVE-2018-15534 being exploited?

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

Public exploit code:

- Geutebrueck re_porter 7.8.974.20 - Credential Disclosure (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2018-15533](https://insights.sbomify.com/CVE-2018-15533/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-15534 and fix it if it is affected.

What it is: CVE-2018-15534 is a critical vulnerability in n/a, published on 21 Aug 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-15534 in the wild and no public exploit code.

Affected product: n/a. 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-2018-15534/ (Markdown: https://insights.sbomify.com/CVE-2018-15534/index.md)
```

## Sources

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

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