CVE-2019-18868

9.8 CRITICAL

📋 TL;DR

CVE-2019-18868 allows unauthenticated attackers to retrieve MySQL database credentials stored in cleartext within Blaauw Remote Kiln Control software files. This affects all systems running vulnerable versions of the kiln control software, potentially exposing sensitive database access.

💻 Affected Systems

Products:
  • Blaauw Remote Kiln Control
Versions: through v3.00r4
Operating Systems: Not specified, likely various
Default Config Vulnerable: ⚠️ Yes
Notes: Vulnerability exists in default installation with cleartext credential files accessible via web server.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers gain full database access, leading to data theft, manipulation of kiln control systems, or complete system compromise through privilege escalation.

🟠

Likely Case

Attackers extract database credentials and access sensitive kiln operation data, potentially modifying configurations or disrupting industrial processes.

🟢

If Mitigated

With proper network segmentation and access controls, impact is limited to credential exposure without direct database access.

🌐 Internet-Facing: HIGH - Unauthenticated access to cleartext credentials makes internet-exposed systems extremely vulnerable to compromise.
🏢 Internal Only: MEDIUM - Internal attackers or compromised internal systems could still exploit this, though attack surface is reduced.

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Simple HTTP requests to vulnerable file paths can retrieve credentials without authentication.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: Not available

Restart Required: No

Instructions:

No official patch available. Remove or secure vulnerable backup files and implement workarounds.

🔧 Temporary Workarounds

Remove vulnerable backup files

all

Delete or restrict access to /engine/db.inc, /lang/nl.bak, and /lang/en.bak files

rm /path/to/webroot/engine/db.inc
rm /path/to/webroot/lang/nl.bak
rm /path/to/webroot/lang/en.bak

Implement web server access controls

linux

Configure web server to deny access to .inc and .bak files

Add to Apache .htaccess: <FilesMatch "\.(inc|bak)$">
  Order allow,deny
  Deny from all
</FilesMatch>
For Nginx: location ~ \.(inc|bak)$ { deny all; }

🧯 If You Can't Patch

  • Implement strict network segmentation to isolate kiln control systems from untrusted networks
  • Deploy web application firewall (WAF) rules to block access to vulnerable file paths

🔍 How to Verify

Check if Vulnerable:

Attempt HTTP GET requests to /engine/db.inc, /lang/nl.bak, and /lang/en.bak on the kiln control web interface

Check Version:

Check software version in web interface or configuration files

Verify Fix Applied:

Verify files are removed or return 403/404 errors, and test that legitimate functionality remains operational

📡 Detection & Monitoring

Log Indicators:

  • HTTP 200 responses to .inc or .bak file requests in web server logs
  • Unusual database connection attempts from web server IP

Network Indicators:

  • HTTP requests to /engine/db.inc, /lang/nl.bak, or /lang/en.bak paths
  • Subsequent MySQL connection attempts from unexpected sources

SIEM Query:

web_access_logs | where url contains "db.inc" or url contains ".bak" | where response_code = 200

🔗 References

📤 Share & Export