# CVE-2017-15044: Missing authorization in n/a

> Remote attackers can bypass access controls to read and modify searchable text in DocuWare Fulltext Search due to insecure default network binding.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Nov 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-xrxm-gfhq-gw84

## What is CVE-2017-15044?

CVE-2017-15044 is a high-severity missing authorization vulnerability in n/a, published on 21 Nov 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The default installation of DocuWare Fulltext Search server through 6.11 allows remote users to connect to and download searchable text from the embedded Solr service, bypassing DocuWare's access control features of the DocuWare user interfaces and API. An attacker can also gain privileges by modifying text. The default installation is unsafe because the server listens on the network interface, not the localhost interface.

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

It affects 1 product.


Products: Docuware Fulltext Server.

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

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

## Is CVE-2017-15044 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-15044 is a high-severity missing authorization vulnerability in n/a, published on 21 Nov 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-15044 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-2017-15044/ (Markdown: https://insights.sbomify.com/CVE-2017-15044/index.md)
```

## Sources

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

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