Little Snitch up to 3.7.3 Installer at.obdev.littlesnitchd.plist Library access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.5 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Little Snitch up to 3.7.3. This impacts an unknown function of the file /Library/LaunchDaemons/at.obdev.littlesnitchd.plist of the component Installer. Performing a manipulation as part of Library results in access control. This vulnerability is cataloged as CVE-2017-2675. The attack must be initiated from a local position. There is no exploit available.
Details
A vulnerability was found in Little Snitch up to 3.7.3. It has been classified as problematic. This affects some unknown functionality of the file /Library/LaunchDaemons/at.obdev.littlesnitchd.plist of the component Installer. The manipulation as part of a Library leads to a access control vulnerability. CWE is classifying the issue as CWE-264. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Little Snitch version 3.0 through 3.7.3 suffer from a local privilege escalation vulnerability in the installer part. The vulnerability is related to the installation of the configuration file "at.obdev.littlesnitchd.plist" which gets installed to /Library/LaunchDaemons.
The bug was discovered 04/03/2017. The weakness was shared 04/06/2017 (Website). It is possible to read the advisory at obdev.at. This vulnerability is uniquely identified as CVE-2017-2675 since 12/01/2016. Attacking locally is a requirement. A authentication is required for exploitation. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.
The vulnerability was handled as a non-public zero-day exploit for at least 3 days. During that time the estimated underground price was around $0-$5k.
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
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.5
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.8
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: No
Availability: 🔍
Status: Not defined
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
12/01/2016 🔍04/03/2017 🔍
04/06/2017 🔍
04/06/2017 🔍
04/06/2017 🔍
08/26/2020 🔍
Sources
Advisory: obdev.atStatus: Not defined
Confirmation: 🔍
CVE: CVE-2017-2675 (🔍)
GCVE (CVE): GCVE-0-2017-2675
GCVE (VulDB): GCVE-100-99339
OSVDB: - CVE-2017-2675 - Little Snitch - Privilege Escalation Issue
Entry
Created: 04/06/2017 23:32Updated: 08/26/2020 12:36
Changes: 04/06/2017 23:32 (58), 08/26/2020 12:36 (3)
Complete: 🔍
Cache ID: 216:753: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.