CVE-2019-3700

LOWNVD 2.92.9—
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 2.9 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 99% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
2.9
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 2.9Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 v3
2.9
EG Score
2.9(medium)
EG Risk
18(Track)
EG Risk 18/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity29% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
1.4%
KEV
Not listed

Published

January 24, 2020

Last Modified

November 21, 2024

References (2)

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 31× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 01:45 UTCEG score recompute
  2. 2026-07-22 22:25 UTCEG score recompute
  3. 2026-07-22 14:05 UTCEPSS rescore
  4. 2026-07-20 17:04 UTCEPSS rescore
  5. 2026-07-19 14:28 UTCEPSS rescore
  6. 2026-07-19 14:28 UTCEPSS rescore
  7. 2026-07-18 10:02 UTCEPSS rescore
  8. 2026-07-16 16:59 UTCEPSS rescore
  9. 2026-07-16 16:59 UTCEPSS rescore
  10. 2026-07-15 16:55 UTCEPSS rescore
  11. 2026-07-15 01:57 UTCEPSS rescore
  12. 2026-07-13 22:27 UTCEPSS rescore
  13. 2026-07-13 22:27 UTCEPSS rescore
  14. 2026-07-12 05:44 UTCEPSS rescore
  15. 2026-07-12 05:43 UTCEPSS rescore
  16. 2026-07-09 19:06 UTCEPSS rescore
  17. 2026-07-08 15:11 UTCEPSS rescore
  18. 2026-07-07 13:43 UTCEPSS rescore
  19. 2026-07-06 02:20 UTCEPSS rescore
  20. 2026-07-06 02:20 UTCEPSS rescore
  21. 2026-07-05 02:27 UTCEPSS rescore
  22. 2026-07-04 06:28 UTCEPSS rescore
  23. 2026-07-01 15:03 UTCEPSS rescore
  24. 2026-07-01 15:03 UTCEPSS rescore
  25. 2026-06-30 23:20 UTCEPSS rescore
Show 56 more
  1. 2026-06-28 14:04 UTCEPSS rescore
  2. 2026-06-28 04:54 UTCEPSS rescore
  3. 2026-06-28 04:54 UTCEPSS rescore
  4. 2026-06-27 03:06 UTCEPSS rescore
  5. 2026-06-23 21:31 UTCEPSS rescore
  6. 2026-06-23 21:31 UTCEPSS rescore
  7. 2026-06-22 14:23 UTCEPSS rescore
  8. 2026-06-22 14:23 UTCEPSS rescore
  9. 2026-06-21 01:57 UTCEPSS rescore
  10. 2026-06-21 01:57 UTCEPSS rescore
  11. 2026-06-19 19:23 UTCEPSS rescore
  12. 2026-06-19 19:23 UTCEPSS rescore
  13. 2026-06-18 17:50 UTCEPSS rescore
  14. 2026-06-18 17:50 UTCEPSS rescore
  15. 2026-06-17 17:50 UTCEPSS rescore
  16. 2026-06-16 17:50 UTCEPSS rescore
  17. 2026-06-15 17:46 UTCEPSS rescore
  18. 2026-06-14 23:15 UTCEPSS rescore
  19. 2026-06-14 23:15 UTCEPSS rescore
  20. 2026-06-13 22:58 UTCEPSS rescore
  21. 2026-06-12 23:09 UTCEPSS rescore
  22. 2026-06-12 23:09 UTCEPSS rescore
  23. 2026-06-11 13:58 UTCEPSS rescore
  24. 2026-06-10 22:16 UTCEPSS rescore
  25. 2026-06-10 22:16 UTCEPSS rescore
  26. 2026-06-10 13:19 UTCEPSS rescore
  27. 2026-06-08 14:15 UTCEPSS rescore
  28. 2026-06-08 14:15 UTCEPSS rescore
  29. 2026-06-08 14:15 UTCEPSS rescore
  30. 2026-06-07 15:23 UTCEPSS rescore
  31. 2026-06-07 15:23 UTCEPSS rescore
  32. 2026-06-06 13:45 UTCEPSS rescore
  33. 2026-06-06 13:45 UTCEPSS rescore
  34. 2026-06-05 22:45 UTCEPSS rescore
  35. 2026-06-05 06:08 UTCEPSS rescore
  36. 2026-06-04 13:10 UTCEPSS rescore
  37. 2026-06-04 13:10 UTCEPSS rescore
  38. 2026-06-02 20:11 UTCEPSS rescore
  39. 2026-06-02 20:11 UTCEPSS rescore
  40. 2026-06-01 13:50 UTCEPSS rescore
  41. 2026-06-01 13:50 UTCEPSS rescore
  42. 2026-05-31 22:29 UTCEPSS rescore
  43. 2026-05-31 22:29 UTCEPSS rescore
  44. 2026-05-31 00:14 UTCEPSS rescore
  45. 2026-05-31 00:14 UTCEPSS rescore
  46. 2026-05-29 13:42 UTCEPSS rescore
  47. 2026-05-28 13:43 UTCEPSS rescore
  48. 2026-05-28 13:43 UTCEPSS rescore
  49. 2026-05-27 13:39 UTCEPSS rescore
  50. 2026-05-27 13:38 UTCEPSS rescore
  51. 2026-05-27 08:44 UTCEG score recompute
  52. 2026-05-27 08:44 UTCGHSA enrichment
  53. 2026-05-26 13:42 UTCEPSS rescore
  54. 2026-05-26 07:17 UTCEPSS rescore
  55. 2026-05-26 07:17 UTCEPSS rescore
  56. 2026-05-26 07:17 UTCEPSS rescore

Frequently asked(5)

What is CVE-2019-3700?
CVE-2019-3700 is a low vulnerability published on January 24, 2020. 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…
When was CVE-2019-3700 disclosed?
CVE-2019-3700 was first published in the National Vulnerability Database on January 24, 2020, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-3700 actively exploited?
CVE-2019-3700 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2019-3700?
CVE-2019-3700 has a CVSS v3 base score of 2.9 (NVD).
How do I remediate CVE-2019-3700?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-3700, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2019-3700

Explore →

Is Your Infrastructure Affected by CVE-2019-3700?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs