# CVE-2019-18864: Information disclosure in n/a

> Unauthenticated attackers can access sensitive host machine information via exposed server-info and server-status endpoints in Blaauw Remote Kiln Control.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 May 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-m7hv-cw89-969h

## What is CVE-2019-18864?

CVE-2019-18864 is a high-severity vulnerability in n/a, published on 7 May 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

/server-info and /server-status in Blaauw Remote Kiln Control through v3.00r4 allow an unauthenticated attacker to gain sensitive information about the host machine.

## Which versions are affected by CVE-2019-18864?

It affects 1 product.


Products: Blaauwproducts Remote Kiln Control.

## How do I fix CVE-2019-18864?

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

## Is CVE-2019-18864 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-18868](https://insights.sbomify.com/CVE-2019-18868/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2019-18869](https://insights.sbomify.com/CVE-2019-18869/): Code injection in n/a (critical 9.8)
- [CVE-2019-18871](https://insights.sbomify.com/CVE-2019-18871/): Path traversal in n/a (high 8.8)
- [CVE-2019-18866](https://insights.sbomify.com/CVE-2019-18866/): SQL injection in n/a (high 7.5)
- [CVE-2019-18867](https://insights.sbomify.com/CVE-2019-18867/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-18864 and fix it if it is affected.

What it is: CVE-2019-18864 is a high-severity vulnerability in n/a, published on 7 May 2020. 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-2019-18864 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-2019-18864/ (Markdown: https://insights.sbomify.com/CVE-2019-18864/index.md)
```

## Sources

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

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