How severe is CVE-2017-20166?

CVE-2017-20166 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2017-20166 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (67th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2017-20166?

CVE-2017-20166 affects Ecto Project Ecto. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2017-20166?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2017-20166 published?

CVE-2017-20166 was published on 2023-01-10 and last updated on 2026-06-17.

CVE-2017-20166

CVE-2017-20166 is a critical-severity vulnerability in Ecto Project Ecto with a CVSS 3.x base score of 9.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-754.

Key facts

Severity: Critical (CVSS 3.x base score 9.8)
EPSS exploit prediction: 1% (67th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-754
Affected product: Ecto Project Ecto
Published: 2023-01-10
Last modified: 2026-06-17

Description

Ecto 2.2.0 lacks a certain protection mechanism associated with the interaction between is_nil and raise.

Frequently asked questions

What is CVE-2017-20166?: Ecto 2.2.0 lacks a certain protection mechanism associated with the interaction between is_nil and raise.
How severe is CVE-2017-20166?: CVE-2017-20166 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2017-20166 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (67th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2017-20166?: CVE-2017-20166 affects Ecto Project Ecto. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2017-20166?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2017-20166 published?: CVE-2017-20166 was published on 2023-01-10 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:ecto_project:ecto:2.2.0:*:*:*:*:*:*:*

Other CWE-754 (Improper Check for Unusual or Exceptional Conditions) vulnerabilities

CVE-2026-24054 — Critical (CVSS 10.0): Kata Containers is an open source project focusing on a standard implementation of lightweight Virtual Machines (VMs)…
CVE-2021-0211 — Critical (CVSS 10.0): An improper check for unusual or exceptional conditions in Juniper Networks Junos OS and Junos OS Evolved Routing…
CVE-2026-8091 — Critical (CVSS 9.8): Incorrect boundary conditions in the Audio/Video: Playback component. This vulnerability was fixed in Firefox 150,…
CVE-2024-52316 — Critical (CVSS 9.8): Unchecked Error Condition vulnerability in Apache Tomcat. If Tomcat is configured to use a custom Jakarta…
CVE-2024-7826 — Critical (CVSS 9.8): Improper Check for Unusual or Exceptional Conditions vulnerability in Webroot SecureAnywhere - Web Shield on Windows,…
CVE-2023-37303 — Critical (CVSS 9.8): An issue was discovered in the CheckUser extension for MediaWiki through 1.39.3. In certain situations, an attempt to…

Browse all CWE-754 (Improper Check for Unusual or Exceptional Conditions) vulnerabilities →