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.
History

No history.

cve-icon MITRE

Status: PUBLISHED

Assigner: suse

Published: 2020-01-24T12:45:14.347248Z

Updated: 2024-09-17T01:26:30.443Z

Reserved: 2019-01-03T00:00:00

Link: CVE-2019-3700

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Analyzed

Published: 2020-01-24T14:15:11.850

Modified: 2020-02-05T15:16:56.527

Link: CVE-2019-3700

cve-icon Redhat

No data.