CVE-2020-15101 json
Nested directory structure can lead to Uncontrolled Resource Consumption in freewvs
published 6y ago modified 4mo ago also GHSA-7pmh-vrww-25xx , PYSEC-2020-233 , EUVD-2020-0082
- cvss
- 2.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 53%
- public exploits
- 0
- none known
Summary
In freewvs before 0.1.1, a directory structure of more than 1000 nested directories can interrupt a freewvs scan due to Python's recursion limit and os.walk(). This can be problematic in a case where an administrator scans the dirs of potentially untrusted users. This has been patched in 0.1.1.
Patch / fix
Is CVE-2020-15101 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.69% chance of exploitation in the next 30 days, higher than 53% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 2.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L |
| NVD | 3.1 | 3.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:N/I:N/A:P |
| GitHub | 3.1 | 2.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | freewvs | <0.1.1 |
0.1.1 |
Affected products
- schokokeksorg freewvs
Classification
References
-
github.com
/schokokeksorg/freewvs/commit/83a6b55c0435c69f447488b791555e6078803143
web, patch, third-party-advisory
-
github.com
/schokokeksorg/freewvs/security/advisories/GHSA-7pmh-vrww-25xx
web, third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-15101
advisory
-
github.com
/pypa/advisory-database/tree/main/vulns/freewvs/PYSEC-2020-233.yaml
web
-
github.com
/schokokeksorg/freewvs
package
Sources
- CVE List CVE-2020-15101
- GitHub Advisory GHSA-7pmh-vrww-25xx
- NVD CVE-2020-15101
- OSV PYSEC-2020-233
Fencer Intel 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.