Zemana Anti-Logger up to 1.9.3.527 MyRules2.ini access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Zemana Anti-Logger up to 1.9.3.527. Affected by this vulnerability is an unknown functionality of the file %LOCALAPPDATA%\Zemana\ZALSDK\MyRules2.ini. This manipulation causes access control. This vulnerability appears as CVE-2018-15491. The attack requires local access. There is no available exploit. You should upgrade the affected component.
Details
A vulnerability classified as critical was found in Zemana Anti-Logger up to 1.9.3.527 (Log Management Software). Affected by this vulnerability is some unknown functionality of the file %LOCALAPPDATA%\Zemana\ZALSDK\MyRules2.ini. The manipulation with an unknown input leads to a access control vulnerability. The CWE definition for the vulnerability is CWE-264. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
A vulnerability in the permission and encryption implementation of Zemana Anti-Logger 1.9.3.527 and prior (fixed in 1.9.3.602) allows an attacker to take control of the whitelisting feature (MyRules2.ini under %LOCALAPPDATA%\Zemana\ZALSDK) to permit execution of unauthorized applications (such as ones that record keystrokes).
The bug was discovered 08/18/2018. The weakness was presented 08/18/2018 (Website). The advisory is shared at github.com. This vulnerability is known as CVE-2018-15491 since 08/17/2018. An attack has to be approached locally. A single authentication is required for exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
By approaching the search of inurl:%LOCALAPPDATA%\Zemana\ZALSDK\MyRules2.ini it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 1.9.3.602 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
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: Access controlCWE: CWE-264
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
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: UpgradeStatus: 🔍
Upgrade: Anti-Logger 1.9.3.602
Timeline
08/17/2018 🔍08/17/2018 🔍
08/18/2018 🔍
08/18/2018 🔍
08/18/2018 🔍
05/02/2023 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2018-15491 (🔍)
GCVE (CVE): GCVE-0-2018-15491
GCVE (VulDB): GCVE-100-123013
X-Force: 148554
Entry
Created: 08/18/2018 10:57Updated: 05/02/2023 14:16
Changes: 08/18/2018 10:57 (59), 03/16/2020 15:15 (1), 05/02/2023 14:16 (4)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.