CVE-2019-3700
Low
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.
SeverityLow
CVSS2.9
Exploit probability—
Product
Suse Yast2-security
PublishedJan 24, 2020
First seenJan 24, 2020
Weakness typeCWE-327CWE-327
How to fix
Update
- suse yast2-security4.2.6 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| suse yast2-security | v < 4.2.6 | 4.2.6 |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
In the Intelligence 360 plan
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.