LXCA up to 1.3.1 Credentials credentials management

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
4.8$0-$5k0.00

Summaryinfo

A vulnerability marked as problematic has been reported in LXCA up to 1.3.1. This affects an unknown function. The manipulation leads to credentials management (Credentials). This vulnerability is uniquely identified as CVE-2017-3763. Local access is required to approach this attack. No exploit exists. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability was found in LXCA up to 1.3.1. It has been rated as problematic. This issue affects an unknown code. The manipulation with an unknown input leads to a credentials management vulnerability (Credentials). Using CWE to declare the problem leads to CWE-255. Impacted is confidentiality. The summary by CVE is:

An attacker who obtains access to the location where the LXCA file system is stored may be able to access credentials of local LXCA accounts in LXCA versions earlier than 1.3.2.

The bug was discovered 09/21/2017. The weakness was disclosed 09/22/2017 (Website). It is possible to read the advisory at support.lenovo.com. The identification of this vulnerability is CVE-2017-3763 since 12/16/2016. Attacking locally is a requirement. A simple authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1552 according to MITRE ATT&CK.

The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $0-$5k.

Upgrading to version 1.3.2 eliminates this vulnerability.

The entry VDB-107028 is pretty similar. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.0
VulDB Meta Temp Score: 4.9

VulDB Base Score: 3.3
VulDB Temp Score: 3.2
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 6.7
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Name: Credentials
Class: Credentials management / Credentials
CWE: CWE-255
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: LXCA 1.3.2

Timelineinfo

12/16/2016 🔍
09/21/2017 +279 days 🔍
09/22/2017 +1 days 🔍
09/22/2017 +0 days 🔍
09/23/2017 +1 days 🔍
11/18/2019 +786 days 🔍

Sourcesinfo

Advisory: support.lenovo.com
Status: Not defined
Confirmation: 🔍

CVE: CVE-2017-3763 (🔍)
GCVE (CVE): GCVE-0-2017-3763
GCVE (VulDB): GCVE-100-107027
See also: 🔍

Entryinfo

Created: 09/23/2017 17:22
Updated: 11/18/2019 21:54
Changes: 09/23/2017 17:22 (59), 11/18/2019 21:54 (2)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!