affected: PyPI
nltk>= 3.9.4—CorpusReader.abspaths()/abspath()and thePlaintextCorpusReader/SyntaxCorpusReaderview methods dynamically reproduced:nltk3.9.4(8/9, scoped-escape checks),3.10.3(wheel, 9/9 checks) andmaster6818767b9(9/9 checks)
Source references (file:line) are to commit 303f6e2b (release tag v3.10.3). Line numbers in the released nltk wheel match this tag exactly; master 6818767b9 contains the same code (pathsec.py renumbered by +44 lines from added hardening comments). In 3.9.4 the same logic exists at earlier line numbers (api.py:222-236 for open(), api.py:161-203 for abspath()/abspaths(), data.py:382-388 for the pointer open, pathsec.py:105-114 for the scoped branch); the affected code is identical.
CorpusReader.open() (nltk/corpus/reader/api.py:235-257) is NLTK's hardened file-access entry point: after a lexical guard it calls validate_path(..., required_root=self._root) (api.py:246-249), and the scoped branch of pathsec.validate_path (nltk/pathsec.py:168-179) resolves symlinks and raises ValueError when the resolved target is not inside the corpus root. The view methods do not use this entry point: PlaintextCorpusReader.words/sents/paras (nltk/corpus/reader/plaintext.py:67-118) and SyntaxCorpusReader.parsed_sents/tagged_sents/sents/tagged_words/words (api.py:473-519) build their streams from self.abspaths(fileids, ...) (api.py:174-217), which only does a lexical self._root.join(fileid) (nltk/data.py:452-469) and returns a FileSystemPathPointer. That pointer is opened via FileSystemPathPointer.open() → pathsec.open(raw_path, "rb") with required_root left at its default None (data.py:438-447, nltk/pathsec.py:752,783), so only the global allowed-roots check runs. The O_NOFOLLOW in _hardened_open (pathsec.py:676-731) protects only the final path component, so an **intermediate-directory symlink...
3.10.4Exploitability
AV:LAC:LPR:LUI:NScope
S:UImpact
C:HI:NA:N5.5/CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NFile System