| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Nylas Mail Lives 2.2.2 and classified as problematic. This affects an unknown part of the file $HOME/.nylas-mail. This manipulation causes permission. The identification of this vulnerability is CVE-2017-1000485. The attack can only be executed locally. There is no exploit available. It is advisable to modify the configuration settings.
Details
A vulnerability has been found in Nylas Mail Lives 2.2.2 and classified as problematic. Affected by this vulnerability is an unknown part of the file $HOME/.nylas-mail. The manipulation with an unknown input leads to a permission vulnerability. The CWE definition for the vulnerability is CWE-275. As an impact it is known to affect confidentiality. The summary by CVE is:
Nylas Mail Lives 2.2.2 uses 0755 permissions for $HOME/.nylas-mail, which allows local users to obtain sensitive authentication information via standard filesystem operations.
The bug was discovered 11/29/2017. The weakness was shared 01/03/2018 (GitHub Repository). The advisory is shared at github.com. This vulnerability is known as CVE-2017-1000485 since 01/03/2018. An attack has to be approached locally. A single authentication is necessary for exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1222 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 35 days. During that time the estimated underground price was around $0-$5k.
It is possible to mitigate the problem by applying the configuration setting .
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: 5.5VulDB Meta Temp Score: 5.4
VulDB Base Score: 3.3
VulDB Temp Score: 3.0
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: PermissionCWE: CWE-275 / CWE-266
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: ConfigStatus: 🔍
0-Day Time: 🔍
Timeline
11/29/2017 🔍01/03/2018 🔍
01/03/2018 🔍
01/03/2018 🔍
01/04/2018 🔍
01/20/2023 🔍
Sources
Advisory: 181Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-1000485 (🔍)
GCVE (CVE): GCVE-0-2017-1000485
GCVE (VulDB): GCVE-100-111289
Entry
Created: 01/04/2018 07:28Updated: 01/20/2023 08:21
Changes: 01/04/2018 07:28 (58), 12/19/2019 11:59 (2), 01/20/2023 08:21 (4)
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.