| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.5 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in Ecto 2.2.0. This vulnerability affects unknown code. The manipulation leads to protection mechanism. This vulnerability is documented as CVE-2017-20166. There is not any exploit available. Applying a patch is the recommended action to fix this issue.
Details
A vulnerability was found in Ecto 2.2.0. It has been rated as problematic. This issue affects an unknown code. The manipulation with an unknown input leads to a protection mechanism vulnerability. Using CWE to declare the problem leads to CWE-693. The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product. The impact remains unknown. The summary by CVE is:
Ecto 2.2.0 lacks a certain protection mechanism associated with the interaction between is_nil and raise.
The weakness was released 01/10/2023 as GHSA-2xxx-fhc8-9qvq. The advisory is shared at github.com. The identification of this vulnerability is CVE-2017-20166 since 01/10/2023. Neither technical details nor an exploit are publicly available.
Applying the patch db55b0cba6525c24ebddc88ef9ae0c1c00620250 is able to eliminate this problem. The bugfix is ready for download at github.com.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2023-0331). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.6
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Protection mechanismCWE: CWE-693
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔍
Patch: db55b0cba6525c24ebddc88ef9ae0c1c00620250
Timeline
01/10/2023 🔍01/10/2023 🔍
01/10/2023 🔍
07/02/2025 🔍
Sources
Advisory: GHSA-2xxx-fhc8-9qvqStatus: Confirmed
CVE: CVE-2017-20166 (🔍)
GCVE (CVE): GCVE-0-2017-20166
GCVE (VulDB): GCVE-100-217781
EUVD: 🔍
Entry
Created: 01/10/2023 14:54Updated: 07/02/2025 15:49
Changes: 01/10/2023 14:54 (39), 01/31/2023 08:25 (11), 04/09/2025 20:27 (20), 07/02/2025 15:49 (2)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.