CVE-2019-3700

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
Advertisement

NeevaHost hosting service

Configurations

Configuration 1 (hide)

cpe:2.3:a:suse:yast2-security:*:*:*:*:*:*:*:*

Information

Published : 2020-01-24 06:15

Updated : 2020-02-05 07:16


NVD link : CVE-2019-3700

Mitre link : CVE-2019-3700


JSON object : View

CWE
CWE-327

Use of a Broken or Risky Cryptographic Algorithm

Advertisement

dedicated server usa

Products Affected

suse

  • yast2-security