NASCENT RemKon Device Manager 4.0.0.0 Log maintenance/readLog.php pathname traversal
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.5 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in NASCENT RemKon Device Manager 4.0.0.0 and classified as critical. This affects an unknown function of the file maintenance/readLog.php of the component Log Handler. This manipulation causes pathname traversal. This vulnerability is tracked as CVE-2021-38612. No exploit exists.
Details
A vulnerability classified as problematic was found in NASCENT RemKon Device Manager 4.0.0.0. Affected by this vulnerability is an unknown part of the file maintenance/readLog.php of the component Log Handler. The manipulation with an unknown input leads to a pathname traversal vulnerability. The CWE definition for the vulnerability is CWE-21. As an impact it is known to affect confidentiality.
The weakness was disclosed 08/24/2021. It is possible to read the advisory at blacklanternsecurity.com. This vulnerability is known as CVE-2021-38612. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1006 according to MITRE ATT&CK.
By approaching the search of inurl:maintenance/readLog.php 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.
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: 3.5VulDB Meta Temp Score: 3.5
VulDB Base Score: 3.5
VulDB Temp Score: 3.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: 🔍
Exploiting
Class: Pathname traversalCWE: CWE-21 / CWE-22
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
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
08/12/2021 🔍08/24/2021 🔍
08/24/2021 🔍
08/26/2021 🔍
Sources
Advisory: blacklanternsecurity.comStatus: Confirmed
Confirmation: 🔍
CVE: CVE-2021-38612 (🔍)
GCVE (CVE): GCVE-0-2021-38612
GCVE (VulDB): GCVE-100-181387
Entry
Created: 08/24/2021 18:06Updated: 08/26/2021 15:45
Changes: 08/24/2021 18:06 (38), 08/26/2021 15:45 (2)
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.