CVE-2019-3700
lowpriority · track · 13OT risk · elevatedEPSS 0.001 · 1 %ileEUUSEPSS · scored 2026-10-27
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.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (2)
Products and version ranges known to be affected.
also known as (3)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (5)
External citations — patches, advisories, analysis.
- https://bugzilla.suse.com/show_bug.cgi?id=1157541cnnvd
- https://github.com/yast/yast-security/pull/61Patchcnnvd
- https://nvd.nist.gov/vuln/detail/CVE-2019-3700cnnvd
- https://bugzilla.suse.com/show_bug.cgi?id=1157541enisa_euvd
- https://bugzilla.suse.com/show_bug.cgi?id=1157541Issue TrackingVendor Advisorynvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan