CVE-2017-20166 Ecto missing `is_nil` requirement
Critical 9.8
Published
Updated
Check this codebase for CVE-2017-20166 and fix it if it is affected.
What it is: CVE-2017-20166 is a critical vulnerability in n/a, published on 10 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-20166 exists.
Affected packages and fixed versions:
- ecto (Hex): affected from 2.2.0; fixed in 2.2.1
- ecto (Hex): affected from 2.2.0; fixed in 2.2.1
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2017-20166/ (Markdown: https://insights.sbomify.com/CVE-2017-20166/index.md)
Ecto library lacks protection in is_nil and raise interaction, potentially causing denial of service.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2017-20166?
CVE-2017-20166 is a critical vulnerability in n/a, published on 10 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Ecto 2.2.0 lacks a certain protection mechanism associated with the interaction between is_nil and raise.
Weakness: CWE-754
Which versions are affected by CVE-2017-20166?
2 open source packages ship an affected version, including ecto. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
ecto Hex | From 2.2.0 | 2.2.1 |
ecto Hex | From 2.2.0 | 2.2.1 |
Products include Ecto Project Ecto.
How do I fix CVE-2017-20166?
Upgrade ecto to 2.2.1 or later.
Is CVE-2017-20166 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-20166 exists.
Sources
Also known as GHSA-2xxx-fhc8-9qvq.