PSF-2019-17 http.cookiejar: Incorrect validation of path
Not scored
Published
Check this codebase for PSF-2019-17 and fix it if it is affected.
What it is: PSF-2019-17 is a vulnerability, published on 3 Jan 2019. 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-2019-17 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-2019-17/ (Markdown: https://insights.sbomify.com/PSF-2019-17/index.md)
Incorrect path validation in Python's http.cookiejar allows cookies to be sent to unintended subpaths, potentially leaking sensitive data.
- 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-2019-17?
PSF-2019-17 is a vulnerability, published on 3 Jan 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Cookies of
example.com with path=/any were sent to
example.com/anybad/ while using a cookiejar with
http.cookiejar.DefaultCookiePolicy policy. The code did not check for
the first non-matching character in prefix match to be a slash.Which versions are affected by PSF-2019-17?
How do I fix PSF-2019-17?
No fix has been published for PSF-2019-17 yet. Limit exposure of the affected software until one is available.
Is PSF-2019-17 being exploited?
There is no known exploitation of PSF-2019-17 in the wild and no public exploit code.