NLTK version 3.9.4 is vulnerable to a path traversal attack due to an incomplete fix for GitHub Issue #3504. The `_UNSAFE_NO_PROTOCOL_RE` regex in `nltk/data.py` checks for literal `../` sequences but fails to account for percent-encoded traversal sequences such as `..%2f`. The `url2pathname()` function decodes these sequences after the validation step, allowing an attacker to bypass the protection. This vulnerability enables an attacker to read arbitrary files accessible to the Python process by controlling the resource name parameter passed to `nltk.data.load()` or `nltk.data.find()`. The issue affects applications that rely on NLTK for resource loading, including NLP web applications, Jupyter notebooks, and CLI tools. The default `pathsec.ENFORCE=False` setting exacerbates the impact by not blocking the file read at the `open()` stage.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NNltk
APPNltk3.9.4
Related vulnerabilities
RCE w NLTK StanfordSegmenter — ładowanie niezweryfikowanych plików JAR
NLTK (Natural Language Toolkit) is a suite of open source Python modules, data sets, and tutorials supporting ...
NLTK (Natural Language Toolkit) is a suite of open source Python modules, data sets, and tutorials supporting ...
NLTK (Natural Language Toolkit) is a suite of open source Python modules, data sets, and tutorials supporting ...
A vulnerability in the `filestring()` function of the `nltk.util` module in nltk version 3.9.2 allows arbitrar...