Description
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.
Analysis
No analysis available yet.
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| openSUSE | Factory | affected |
|
No data.
No data available yet.
Remediation
No remediation available yet.
Tracking
Sign in to view the affected projects.
Advisories
| Source | ID | Title |
|---|---|---|
 EUVD |
EUVD-2019-13335 | 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. |
References
| Link | Providers |
|---|---|
| https://bugzilla.suse.com/show_bug.cgi?id=1157541 |
|
History
No history.
MITRE
Status: PUBLISHED
Assigner: suse
Published:
Updated: 2024-09-17T01:26:30.443Z
Reserved: 2019-01-03T00:00:00.000Z
Link: CVE-2019-3700
Vulnrichment
No data.
NVD
Status : Modified
Published: 2020-01-24T14:15:11.850
Modified: 2024-11-21T04:42:21.667
Link: CVE-2019-3700
Redhat
No data.
OpenCVE Enrichment
No data.
Weaknesses