CVE-2019-3700: yast: Fallback to DES without configuration in /etc/login.def
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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2019-3700?
CVE-2019-3700 is considered a medium severity vulnerability due to insecure password handling.
How does CVE-2019-3700 affect yast2-security?
CVE-2019-3700 affects yast2-security by allowing the use of insecure default settings for password protection.
How can I mitigate the risks associated with CVE-2019-3700?
To mitigate CVE-2019-3700, ensure that secure password handling configurations are applied and verified.
What versions of Suse are affected by CVE-2019-3700?
CVE-2019-3700 affects Suse Yast2-security versions prior to 4.2.6.
Is there a fix available for CVE-2019-3700?
Yes, updating to Suse Yast2-security version 4.2.6 or later addresses the vulnerabilities identified in CVE-2019-3700.