CVE-2019-17006

CRITICALNVD 9.89.8
EchelonGraph scoreLOW confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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: nvd
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 4%CVSS: 9.8Exploit: NoneExposed: 0

A fix is available — apply it.

In Network Security Services (NSS) before 3.46, several cryptographic primitives had missing length checks. In cases where the application calling the library did not perform a sanity check on the inputs it could result in a crash due to a buffer overflow.

CVSS v3
9.8
EG Score
9.8(low)
EPSS
87.9%
KEV
Not listed

Published

October 22, 2020

Last Modified

November 21, 2024

Advisory Details (3)

Auto-updated Jun 22, 2026
Patch available. Sources: cisa.
cisa Patch Available

Siemens RUGGEDCOM ROX II | CISA

https://us-cert.cisa.gov/ics/advisories/icsa-21-040-04
generic

1539788 - (CVE-2019-17006) Check length of inputs for cryptographic primitives

https://bugzilla.mozilla.org/show_bug.cgi?id=1539788

Patch Availability(7)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibnss3-tools (2:3.28.4-0ubuntu0.14.04.5+esm4) @ trusty2026-05-23ubuntu
redhatnss-softokn-0:3.44.0-9.el7_72021-03-30redhat
redhatopenshiftdo/odo-init-image-rhel7:1.1.3-22021-03-22redhat
redhatnss-softokn-0:3.36.0-7.el7_62021-03-16redhat
redhatnss-softokn-0:3.28.3-10.el7_42021-03-09redhat
redhatnss-util-0:3.53.1-1.el7_92020-09-29redhat
redhatnss-0:3.53.1-11.el8_22020-08-03redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(3)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 8× in last 7d / 35× 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-11 08:24 UTCEPSS rescore
  2. 2026-07-11 08:24 UTCEPSS rescore
  3. 2026-07-09 19:06 UTCEPSS rescore
  4. 2026-07-08 15:11 UTCEPSS rescore
  5. 2026-07-06 16:25 UTCEPSS rescore
  6. 2026-07-06 16:25 UTCEPSS rescore
  7. 2026-07-06 02:20 UTCEPSS rescore
  8. 2026-07-05 02:27 UTCEPSS rescore
  9. 2026-07-04 06:28 UTCEPSS rescore
  10. 2026-07-01 15:03 UTCEPSS rescore
  11. 2026-07-01 15:03 UTCEPSS rescore
  12. 2026-06-30 23:20 UTCEPSS rescore
  13. 2026-06-29 14:03 UTCEPSS rescore
  14. 2026-06-28 14:04 UTCEPSS rescore
  15. 2026-06-28 04:54 UTCEPSS rescore
  16. 2026-06-28 04:54 UTCEPSS rescore
  17. 2026-06-27 03:06 UTCEPSS rescore
  18. 2026-06-25 13:47 UTCEPSS rescore
  19. 2026-06-25 13:47 UTCEPSS rescore
  20. 2026-06-24 14:03 UTCEPSS rescore
  21. 2026-06-24 14:03 UTCEPSS rescore
  22. 2026-06-24 09:42 UTCOSV refresh
  23. 2026-06-23 21:31 UTCEPSS rescore
  24. 2026-06-23 21:30 UTCEPSS rescore
  25. 2026-06-22 14:23 UTCEPSS rescore
Show 42 more
  1. 2026-06-21 01:57 UTCEPSS rescore
  2. 2026-06-21 01:57 UTCEPSS rescore
  3. 2026-06-18 17:50 UTCEPSS rescore
  4. 2026-06-17 17:50 UTCEPSS rescore
  5. 2026-06-16 17:50 UTCEPSS rescore
  6. 2026-06-15 17:45 UTCEPSS rescore
  7. 2026-06-14 23:15 UTCEPSS rescore
  8. 2026-06-14 23:15 UTCEPSS rescore
  9. 2026-06-13 22:58 UTCEPSS rescore
  10. 2026-06-12 23:09 UTCEPSS rescore
  11. 2026-06-11 13:58 UTCEPSS rescore
  12. 2026-06-10 22:16 UTCEPSS rescore
  13. 2026-06-10 13:19 UTCEPSS rescore
  14. 2026-06-08 14:15 UTCEPSS rescore
  15. 2026-06-07 15:23 UTCEPSS rescore
  16. 2026-06-07 15:23 UTCEPSS rescore
  17. 2026-06-07 14:30 UTCOSV refresh
  18. 2026-06-06 13:45 UTCEPSS rescore
  19. 2026-06-06 13:45 UTCEPSS rescore
  20. 2026-06-05 22:45 UTCEPSS rescore
  21. 2026-06-05 22:45 UTCEPSS rescore
  22. 2026-06-05 06:08 UTCEPSS rescore
  23. 2026-06-05 06:08 UTCEPSS rescore
  24. 2026-06-04 13:10 UTCEPSS rescore
  25. 2026-06-04 13:10 UTCEPSS rescore
  26. 2026-06-02 20:11 UTCEPSS rescore
  27. 2026-06-02 20:11 UTCEPSS rescore
  28. 2026-06-01 13:50 UTCEPSS rescore
  29. 2026-06-01 13:50 UTCEPSS rescore
  30. 2026-05-31 22:29 UTCEPSS rescore
  31. 2026-05-31 22:29 UTCEPSS rescore
  32. 2026-05-31 00:14 UTCEPSS rescore
  33. 2026-05-31 00:14 UTCEPSS rescore
  34. 2026-05-29 13:42 UTCEPSS rescore
  35. 2026-05-28 13:43 UTCEPSS rescore
  36. 2026-05-27 13:38 UTCEPSS rescore
  37. 2026-05-26 07:17 UTCEPSS rescore
  38. 2026-05-26 07:17 UTCEPSS rescore
  39. 2026-05-26 07:17 UTCEPSS rescore
  40. 2026-05-23 06:09 UTCEG score recompute
  41. 2026-05-23 06:09 UTCVendor advisory
  42. 2026-05-23 06:09 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2019-17006?
CVE-2019-17006 is a critical vulnerability published on October 22, 2020. In Network Security Services (NSS) before 3.46, several cryptographic primitives had missing length checks. In cases where the application calling the library did not perform a sanity check on the inputs it could result in a crash due to a buffer overflow.
When was CVE-2019-17006 disclosed?
CVE-2019-17006 was first published in the National Vulnerability Database on October 22, 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-17006 actively exploited?
CVE-2019-17006 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 87.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2019-17006?
CVE-2019-17006 has a CVSS v3 base score of 9.8 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2019-17006?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-17006, 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-17006

Explore →

Is Your Infrastructure Affected by CVE-2019-17006?

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