Adiscon LogAnalyzer up to 4.1.6 Login Button Referer Field login.php cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.0 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Adiscon LogAnalyzer up to 4.1.6. It has been declared as problematic. Affected by this issue is some unknown functionality of the file login.php of the component Login Button Referer Field. Executing a manipulation can lead to cross site scripting. This vulnerability is handled as CVE-2018-19877. The attack can be executed remotely. Additionally, an exploit exists. It is recommended to upgrade the affected component.
Details
A vulnerability was found in Adiscon LogAnalyzer up to 4.1.6. It has been declared as problematic. This vulnerability affects some unknown processing of the file login.php of the component Login Button Referer Field. The manipulation with an unknown input leads to a cross site scripting vulnerability. The CWE definition for the vulnerability is CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. As an impact it is known to affect integrity. CVE summarizes:
login.php in Adiscon LogAnalyzer before 4.1.7 has XSS via the Login Button Referer field.
The bug was discovered 12/05/2018. The weakness was released 12/05/2018 (Website). The advisory is available at loganalyzer.adiscon.com. This vulnerability was named CVE-2018-19877 since 12/05/2018. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Successful exploitation requires user interaction by the victim. Technical details and also a public exploit are known. This vulnerability is assigned to T1059.007 by the MITRE ATT&CK project.
It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:login.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 4.1.7 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at Exploit-DB (45958). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.2VulDB Meta Temp Score: 5.0
VulDB Base Score: 4.3
VulDB Temp Score: 3.9
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.1
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: Cross site scriptingCWE: CWE-79 / CWE-94 / CWE-74
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: LogAnalyzer 4.1.7
Timeline
12/05/2018 🔍12/05/2018 🔍
12/05/2018 🔍
12/05/2018 🔍
12/06/2018 🔍
03/20/2025 🔍
Sources
Advisory: loganalyzer.adiscon.comStatus: Confirmed
CVE: CVE-2018-19877 (🔍)
GCVE (CVE): GCVE-0-2018-19877
GCVE (VulDB): GCVE-100-127546
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 12/06/2018 08:20Updated: 03/20/2025 20:37
Changes: 12/06/2018 08:20 (62), 04/17/2020 20:54 (4), 03/20/2025 20:37 (18)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.