Webgalamb up to 7.0 Log File YYYY-MM-DD-sql_error_log.log log file
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, was found in Webgalamb up to 7.0. Affected by this issue is some unknown functionality of the file files/logs/sql_error_log/YYYY-MM-DD-sql_error_log.log of the component Log File. Such manipulation leads to log file. This vulnerability is traded as CVE-2018-19513. The attack may be launched remotely. There is no exploit available.
Details
A vulnerability, which was classified as problematic, has been found in Webgalamb up to 7.0. Affected by this issue is some unknown functionality of the file files/logs/sql_error_log/YYYY-MM-DD-sql_error_log.log of the component Log File. The manipulation with an unknown input leads to a log file vulnerability. Using CWE to declare the problem leads to CWE-532. Information written to log files can be of a sensitive nature and give valuable guidance to an attacker or expose sensitive user information. Impacted is confidentiality. CVE summarizes:
In Webgalamb through 7.0, log files are exposed to the internet with predictable files/logs/sql_error_log/YYYY-MM-DD-sql_error_log.log filenames. The log file could contain sensitive client data (email addresses) and also facilitates exploitation of SQL injection errors.
The bug was discovered 01/02/2019. The weakness was shared 03/21/2019. This vulnerability is handled as CVE-2018-19513 since 11/23/2018. The attack may be launched remotely. No form of authentication is required for exploitation. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1592.
The vulnerability was handled as a non-public zero-day exploit for at least 78 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:files/logs/sql_error_log/YYYY-MM-DD-sql_error_log.log it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-131926, VDB-131925, VDB-131923 and VDB-131922 are related to this item. Once again VulDB remains the best source for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
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
Class: Log fileCWE: CWE-532 / CWE-200 / CWE-284
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
Google Hack: 🔍
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/23/2018 🔍01/02/2019 🔍
03/21/2019 🔍
03/21/2019 🔍
08/03/2023 🔍
Sources
Advisory: 151017Status: Not defined
CVE: CVE-2018-19513 (🔍)
GCVE (CVE): GCVE-0-2018-19513
GCVE (VulDB): GCVE-100-131924
See also: 🔍
Entry
Created: 03/21/2019 22:56Updated: 08/03/2023 14:10
Changes: 03/21/2019 22:56 (55), 05/17/2020 21:44 (1), 08/03/2023 14:04 (4), 08/03/2023 14:10 (1)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.