PSF-2016-10 gettext.c2py()
Not scored
Published
Check this codebase for PSF-2016-10 and fix it if it is affected.
What it is: PSF-2016-10 is a code injection vulnerability, published on 30 Oct 2016.
Exploitation: There is no known exploitation of PSF-2016-10 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-2016-10/ (Markdown: https://insights.sbomify.com/PSF-2016-10/index.md)
Arbitrary code execution is possible via the gettext.c2py() function in the Python gettext library.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Not stated
- Victim action needed
- Not needed
- Fix
- None listed
What is PSF-2016-10?
PSF-2016-10 is a code injection vulnerability, published on 30 Oct 2016.
Official description
Arbitrary code execution in
gettext.c2py().Which versions are affected by PSF-2016-10?
How do I fix PSF-2016-10?
No fix has been published for PSF-2016-10 yet. Limit exposure of the affected software until one is available.
Upgrade, and never evaluate templates, expressions or code built from user input. More about Code injection.
Is PSF-2016-10 being exploited?
There is no known exploitation of PSF-2016-10 in the wild and no public exploit code.