{"answers":{"affected":"","exploited":"There is no known exploitation of PSF-2021-5 in the wild and no public exploit code.","fix":"No fix has been published for PSF-2021-5 yet. Limit exposure of the affected software until one is available.","what":"PSF-2021-5 is a server-side request forgery vulnerability, published on 21 Feb 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for PSF-2021-5 and fix it if it is affected.\n\nWhat it is: PSF-2021-5 is a server-side request forgery vulnerability, published on 21 Feb 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of PSF-2021-5 in the wild and no public exploit code.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/PSF-2021-5/ (Markdown: https://insights.sbomify.com/PSF-2021-5/index.md)","id":"PSF-2021-5","markdown":"https://insights.sbomify.com/PSF-2021-5/index.md","name":"PSF-2021-5","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Python ftplib library","requires_auth":"none","summary":"A malicious FTP server can force the client to probe internal network addresses via PASV response, enabling SSRF-like attacks.","user_interaction":"required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"The IPv4 address value returned from the server in response to the PASV\ncommand should not be trusted. This prevents a malicious FTP server from\nusing the response to probe IPv4 address and port combinations on the\nclient network.\n\nInstead of using the returned address, we use the IP address we're already\nconnected to. This is the strategy other ftp clients adopted, and matches\nthe only strategy available for the modern IPv6 EPSV command where the\nserver response must return a port number and nothing else.","ecosystems":[],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":false,"headline":"ftplib should not use the host from the PASV response","id":"PSF-2021-5","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2021"},"n_packages":0,"n_references":null,"packages":[],"products":null,"published":"2021-02-21","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"Python Software Foundation","prefix":"PSF"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"A malicious FTP server can force the client to probe internal network addresses via PASV response, enabling SSRF-like attacks.","url":"https://insights.sbomify.com/PSF-2021-5/"}