# CVE-2019-18868: Hardcoded credentials in n/a

> Unauthenticated attackers can access cleartext MySQL credentials in backup files, leading to database compromise.

- **Severity:** Critical 9.8 (`CVSS:3.1/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:** 7 May 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-cgf9-gjp4-6wg6

## What is CVE-2019-18868?

CVE-2019-18868 is a critical 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

Blaauw Remote Kiln Control through v3.00r4 allows an unauthenticated attacker to access MySQL credentials in cleartext in /engine/db.inc, /lang/nl.bak, or /lang/en.bak.

Weakness: CWE-522 (Insufficiently Protected Credentials), CWE-312 (Cleartext Storage of Sensitive Information)

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

It affects 1 product.


Products: Blaauwproducts Remote Kiln Control.

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

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

## Is CVE-2019-18868 being exploited?

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

## Other vulnerabilities in n/a

- [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-18864](https://insights.sbomify.com/CVE-2019-18864/): Information disclosure in n/a (high 7.5)
- [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-18868 and fix it if it is affected.

What it is: CVE-2019-18868 is a critical 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-18868 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-18868/ (Markdown: https://insights.sbomify.com/CVE-2019-18868/index.md)
```

## Sources

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

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