PSF-2013-3 CGI directory traversal (URL parsing)
Not scored
Published
Check this codebase for PSF-2013-3 and fix it if it is affected.
What it is: PSF-2013-3 is a path traversal vulnerability, published on 29 Oct 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of PSF-2013-3 in the wild and no public exploit code.
Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/PSF-2013-3/ (Markdown: https://insights.sbomify.com/PSF-2013-3/index.md)
Remote attackers can execute arbitrary binaries via path traversal in the Python CGI HTTP server handler.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is PSF-2013-3?
PSF-2013-3 is a path traversal vulnerability, published on 29 Oct 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
An error in separating the path and filename of the CGI script to run in
http.server.CGIHTTPRequestHandler allows running arbitrary executables
in the directory under which the server was started.Which versions are affected by PSF-2013-3?
How do I fix PSF-2013-3?
No fix has been published for PSF-2013-3 yet. Limit exposure of the affected software until one is available.
Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.
Is PSF-2013-3 being exploited?
There is no known exploitation of PSF-2013-3 in the wild and no public exploit code.