# CVE-2017-6866: Missing authorization in XHQ 4 (All versions before V4.7.1.3), XHQ 5 (All versions before V5.0.0.2)

> Authenticated low-privileged users can access data beyond their permissions in Siemens XHQ server, requiring an upgrade to secure data confidentiality.

- **Severity:** Medium 6.5 (`CVSS:3.0/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:** 7 Aug 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-m678-x6cm-7g4w

## What is CVE-2017-6866?

CVE-2017-6866 is a medium-severity missing authorization vulnerability in XHQ 4 (All versions before V4.7.1.3), XHQ 5 (All versions before V5.0.0.2), published on 7 Aug 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was discovered in Siemens XHQ server 4 and 5 (4 before V4.7.1.3 and 5 before V5.0.0.2) that could allow an authenticated low-privileged remote user to gain read access to data in the XHQ solution exceeding his configured permission level.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Siemens Xhq Server.

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

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

## Is CVE-2017-6866 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-6866 is a medium-severity missing authorization vulnerability in XHQ 4 (All versions before V4.7.1.3), XHQ 5 (All versions before V5.0.0.2), published on 7 Aug 2017. 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-6866 in the wild and no public exploit code.

Affected product: XHQ 4 (All versions before V4.7.1.3), XHQ 5 (All versions before V5.0.0.2). 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-6866/ (Markdown: https://insights.sbomify.com/CVE-2017-6866/index.md)
```

## Sources

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

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