SmartLine DeviceLock 5.72/5.73 Build 288/5.73 Build 300/5.73 Build 303 Access Control List information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in SmartLine DeviceLock 5.72/5.73 Build 288/5.73 Build 300/5.73 Build 303. Impacted is an unknown function of the component Access Control List. The manipulation leads to information disclosure. This vulnerability is uniquely identified as CVE-2006-4184. No exploit exists. You should upgrade the affected component.
Details
A vulnerability, which was classified as problematic, has been found in SmartLine DeviceLock 5.72/5.73 Build 288/5.73 Build 300/5.73 Build 303. This issue affects some unknown functionality of the component Access Control List. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. The summary by CVE is:
SmartLine DeviceLock before 5.73 Build 305 does not properly enforce access control lists (ACL) in raw mode, which allows local users to bypass NTFS controls and obtain sensitive information.
The weakness was disclosed 08/16/2006 by seppi (Website). The advisory is shared at securityfocus.com. The identification of this vulnerability is CVE-2006-4184 since 08/16/2006. The exploitation is known to be easy. An attack has to be approached locally. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
Upgrading to version 5.73 eliminates this vulnerability.
The vulnerability is also documented in the databases at X-Force (28384), SecurityFocus (BID 19500†) and Secunia (SA21494†). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.2VulDB Meta Temp Score: 5.4
VulDB Base Score: 6.2
VulDB Temp Score: 5.4
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Unproven
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: 🔍
0-Day Time: 🔍
Upgrade: DeviceLock 5.73
Timeline
07/14/2006 🔍08/16/2006 🔍
08/16/2006 🔍
08/16/2006 🔍
08/16/2006 🔍
03/12/2015 🔍
08/02/2018 🔍
Sources
Advisory: securityfocus.com⛔Researcher: seppi
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2006-4184 (🔍)
GCVE (CVE): GCVE-0-2006-4184
GCVE (VulDB): GCVE-100-31817
X-Force: 28384 - SmartLine DeviceLock NTFS ACL bypass
SecurityFocus: 19500 - SmartLine DeviceLock Unauthorized Access Vulnerability
Secunia: 21494 - DeviceLock Device Object Improper Restriction Weakness, Not Critical
Entry
Created: 03/12/2015 15:51Updated: 08/02/2018 09:11
Changes: 03/12/2015 15:51 (60), 08/02/2018 09:11 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.