CVE-2017-20166 json
Ecto missing `is_nil` requirement
published 2022-04-12 4 y ago modified 2026-07-08 4 mo ago also GHSA-2xxx-fhc8-9qvq , EUVD-2023-0331
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 70%
- public exploits
- 0
- none known
Summary
Ecto 2.2.0 lacks a certain protection mechanism associated with the interaction between is_nil and raise.
Patch / fix
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- total
- Assessed
- 19 mo ago
Exploit prediction
1.32% chance of exploitation in the next 30 days, higher than 70% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/elixir-ecto/ecto/pull/2125 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| hex | ecto | >=2.2.0, <2.2.1 |
2.2.1 |
Classification
- Weakness
-
- CWE-754 Improper Check for Unusual or Exceptional Conditions
References
-
github.com
/elixir-ecto/ecto/pull/2125
web, exploit, third-party-advisory
-
github.com
/elixir-ecto/ecto/commit/db55b0cba6525c24ebddc88ef9ae0c1c00620250
web, patch, third-party-advisory
-
github.com
/advisories/GHSA-2xxx-fhc8-9qvq
third-party-advisory
- groups.google.com /forum/#%21topic/elixir-ecto/0m4NPfg_MMU
-
nvd.nist.gov
/vuln/detail/CVE-2017-20166
advisory
-
github.com
/elixir-ecto/ecto
package
-
groups.google.com
/forum/#!topic/elixir-ecto/0m4NPfg_MMU
web
Sources
- CVE List CVE-2017-20166
- GitHub Advisory GHSA-2xxx-fhc8-9qvq
- NVD CVE-2017-20166
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.