CONTENTUM.COMA specialist. A plan. A result.

Vulnerabilities · 2019 · Suse

CVE-2019-3700
Suse Yast2-security vulnerability

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 products

Yast2-security. The exact versions are in the references.

What to do now

  • Check your exposureFind out whether Suse Yast2-security runs anywhere in your environment, including systems of suppliers.
  • UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
  • Set the orderSystems that can be reached from the internet come first, then the rest.

References

More vulnerabilities in Suse products

Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.