| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.7 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in Ayatana Unity up to 7.2.0. The impacted element is an unknown function of the component Lock Screen. The manipulation leads to access control. This vulnerability is listed as CVE-2014-3202. There is no available exploit. It is recommended to upgrade the affected component.
Details
A vulnerability was found in Ayatana Unity up to 7.2.0 and classified as problematic. This issue affects some unknown processing of the component Lock Screen. The manipulation with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-264. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Unity before 7.2.1 does not properly handle entry activation, which allows physically proximate attackers to bypass the lock screen by holding the ENTER key, which triggers the process to crash.
The weakness was presented 05/06/2014 (Website). The advisory is shared at bugs.launchpad.net. The identification of this vulnerability is CVE-2014-3202 since 05/03/2014. 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 T1068 for this issue.
Upgrading to version 7.1.0 eliminates this vulnerability.
See VDB-69594 for similar entry. 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.9VulDB Meta Temp Score: 5.7
VulDB Base Score: 5.9
VulDB Temp Score: 5.7
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: 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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Unity 7.1.0
Timeline
05/03/2014 🔍05/06/2014 🔍
05/06/2014 🔍
03/25/2015 🔍
03/09/2019 🔍
Sources
Advisory: bugs.launchpad.netStatus: Not defined
Confirmation: 🔍
CVE: CVE-2014-3202 (🔍)
GCVE (CVE): GCVE-0-2014-3202
GCVE (VulDB): GCVE-100-69593
See also: 🔍
Entry
Created: 03/25/2015 16:45Updated: 03/09/2019 15:21
Changes: 03/25/2015 16:45 (48), 03/09/2019 15:21 (2)
Complete: 🔍
Cache ID: 216:876: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.