CVE-2018-1000523 json
Topydo Improper Input Validation vulnerability
published 8y ago modified 4mo ago also GHSA-h6h9-pphv-m266 , PYSEC-2018-76 , EUVD-2018-0140
- cvss
- 8.1
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 67%
- public exploits
- 0
- none known
Summary
topydo contains a CWE-20: Improper Input Validation vulnerability in ListFormatParser::parse, file topydo/lib/ListFormat.py line 292 as of d4f843dac71308b2f29a7c2cdc76f055c3841523 that can result in Injection of arbitrary bytes to the terminal, including terminal escape code sequences. This attack appear to be exploitable via The victim must open a todo.txt with at least one specially crafted line..
Is CVE-2018-1000523 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
1.15% chance of exploitation in the next 30 days, higher than 67% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.1 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H |
| NVD | 2.0 | 5.8 | AV:N/AC:M/Au:N/C:N/I:P/A:P |
| GitHub | 3.0 | 8.1 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | topydo | <=0.13 all versions |
no fix listed |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
github.com
/bram85/topydo/issues/240
web, third-party-advisory, report
-
github.com
/bram85/topydo/blob/master/topydo/lib/ListFormat.py#L292
web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2018-1000523
advisory
-
github.com
/advisories/GHSA-h6h9-pphv-m266
advisory
-
github.com
/bram85/topydo
package
-
github.com
/pypa/advisory-database/tree/main/vulns/topydo/PYSEC-2018-76.yaml
web
Sources
- CVE List CVE-2018-1000523
- GitHub Advisory GHSA-h6h9-pphv-m266
- NVD CVE-2018-1000523
- OSV PYSEC-2018-76
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.