| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 2.7 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic was found in yast2-security. Affected is an unknown function. Such manipulation leads to risky encryption. This vulnerability is traded as CVE-2019-3700. An attack has to be approached locally. There is no exploit available. Upgrading the affected component is advised.
Details
A vulnerability was found in yast2-security and classified as problematic. Affected by this issue is an unknown function. The manipulation with an unknown input leads to a risky encryption vulnerability. Using CWE to declare the problem leads to CWE-327. The product uses a broken or risky cryptographic algorithm or protocol. Impacted is confidentiality. CVE summarizes:
yast2-security didn't use secure defaults to protect passwords. This became a problem on 2019-10-07 when configuration files that set secure settings were moved to a different location. As of the 20191022 snapshot the insecure default settings were used until yast2-security switched to stronger defaults in 4.2.6 and used the new configuration file locations. Password created during this time used DES password encryption and are not properly protected against attackers that are able to access the password hashes.
The issue has been introduced in 10/07/2019. The weakness was shared 01/24/2020 as Bug 1157541 as not defined bug report (Bugzilla). The advisory is shared for download at bugzilla.suse.com. This vulnerability is handled as CVE-2019-3700 since 01/03/2019. The exploitation is known to be difficult. The attack needs to be approached locally. The successful exploitation requires a simple authentication. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1600.
The vulnerability was handled as a non-public zero-day exploit for at least 109 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 4.2.6 eliminates this vulnerability.
Once again VulDB remains the best source for vulnerability data.
Product
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 2.8VulDB Meta Temp Score: 2.7
VulDB Base Score: 2.5
VulDB Temp Score: 2.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 2.9
NVD Vector: 🔍
CNA Base Score: 2.9
CNA Vector (SUSE): 🔍
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: Risky encryptionCWE: CWE-327 / CWE-310
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: yast2-security 4.2.6
Timeline
01/03/2019 🔍10/07/2019 🔍
01/24/2020 🔍
01/25/2020 🔍
03/26/2024 🔍
Sources
Advisory: Bug 1157541Status: Not defined
CVE: CVE-2019-3700 (🔍)
GCVE (CVE): GCVE-0-2019-3700
GCVE (VulDB): GCVE-100-149324
Entry
Created: 01/25/2020 08:47Updated: 03/26/2024 08:18
Changes: 01/25/2020 08:47 (40), 01/25/2020 08:52 (11), 03/26/2024 08:18 (34)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.