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 | Resource |
---|---|
https://bugzilla.suse.com/show_bug.cgi?id=1157541 | Issue Tracking Vendor Advisory |
https://bugzilla.suse.com/show_bug.cgi?id=1157541 | Issue Tracking Vendor Advisory |
Configurations
History
21 Nov 2024, 04:42
Type | Values Removed | Values Added |
---|---|---|
References | () https://bugzilla.suse.com/show_bug.cgi?id=1157541 - Issue Tracking, Vendor Advisory | |
CVSS |
v2 : v3 : |
v2 : 2.1
v3 : 2.9 |
Information
Published : 2020-01-24 14:15
Updated : 2024-11-21 04:42
NVD link : CVE-2019-3700
Mitre link : CVE-2019-3700
CVE.ORG link : CVE-2019-3700
JSON object : View
Products Affected
suse
- yast2-security
CWE
CWE-327
Use of a Broken or Risky Cryptographic Algorithm