Blaauw Remote Kiln Control up to v3.00r4 /engine/db.inc Credentials insufficiently protected credentials
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.5 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in Blaauw Remote Kiln Control up to v3.00r4. This issue affects some unknown processing of the file /engine/db.inc. Performing a manipulation results in insufficiently protected credentials (Credentials). This vulnerability is identified as CVE-2019-18868. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability was found in Blaauw Remote Kiln Control up to v3.00r4. It has been classified as problematic. This affects an unknown code of the file /engine/db.inc. The manipulation with an unknown input leads to a insufficiently protected credentials vulnerability (Credentials). CWE is classifying the issue as CWE-522. The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval. This is going to have an impact on confidentiality. The summary by CVE is:
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.
The weakness was released 05/07/2020. This vulnerability is uniquely identified as CVE-2019-18868 since 11/11/2019. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1552 according to MITRE ATT&CK.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Entries connected to this vulnerability are available at VDB-154855, VDB-154854, VDB-154853 and VDB-154852. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.6
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Name: CredentialsClass: Insufficiently protected credentials / Credentials
CWE: CWE-522
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
11/11/2019 🔍05/07/2020 🔍
05/08/2020 🔍
05/08/2020 🔍
Sources
Status: Not definedCVE: CVE-2019-18868 (🔍)
GCVE (CVE): GCVE-0-2019-18868
GCVE (VulDB): GCVE-100-154851
See also: 🔍
Entry
Created: 05/08/2020 08:29Updated: 05/08/2020 08:34
Changes: 05/08/2020 08:29 (37), 05/08/2020 08:34 (17)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.