CVE-2019-3700

lowpriority · track · 13OT risk · elevatedEPSS 0.001 · 1 %ileEUUS
grimoire priorityP3 · Track
Exploitable?
—
no known exploitation
Likely / severe?
0.11% (1st) EPSS
CVSS 2.1 · low
Is it mine?
2 products
Check your exposure
Who says so?
3 sources
cnnvd · enisa_euvd · nvd

EPSS · 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.

01

cvss

Technical severity, 0–10. One row per scoring source.

3.3
010

base score 0–10 · higher = more severe · hover a vector to decode

v2.02.1lowAV:L/AC:L/Au:N/C:P/I:N/A:Nprimary · NVD / NIST USexploitability 3.9 · impact 2.9
v3.13.3lowCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:Nprimary · NVD / NIST USexploitability 1.8 · impact 1.4
v3.12.9lowCVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:Nsecondary · ENISA EU
v3.12.9lowCVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:Nsecondary · meissner@suse.deexploitability 1.4 · impact 1.4
v3.13.1lowCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N/E:Usecondary · CVSS-BT (t0sche)
02

weaknesses

The CWE weakness classes this flaw belongs to.

03

affected products (2)

Products and version ranges known to be affected.

04

also known as (3)

Other names and identifiers for this entity.

05

sources

Which sources assert this record, and when.

published 2020-01-24modified 2026-06-17
07

references (5)

External citations — patches, advisories, analysis.

scry

Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.

Free scan