CyberRota Analysis
AI-GeneratedNLTK versions prior to 3.10.3 are vulnerable to a server-side request forgery (SSRF) flaw when an HTTP proxy is configured, allowing attackers to exploit the proxy to access internal services that should be protected. This vulnerability can lead to the disclosure of sensitive internal resources and the potential installation of malicious packages. Organizations using NLTK, particularly those with proxy configurations, should prioritize upgrading to mitigate the risk of exploitation.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
NLTK before 3.10.3 contains a server-side request forgery vulnerability in nltk.pathsec.urlopen (and callers nltk.data.load, nltk.downloader.Downloader.index/download) when an HTTP proxy is configured. pathsec.urlopen validates the requested hostname locally, but proxy-handler inheritance disables the safe HTTP/HTTPS handlers so the actual fetch is performed by the proxy against a destination that is never re-validated. An attacker can supply a validated public URL that the proxy forwards to an internal loopback-only service, allowing disclosure of internal HTTP resources, loading of forged downloader indexes, and installation of attacker-chosen package content.
Related CVEs
Other vulnerabilities affecting the same vendor(s)