CVE-2022-34500 Supply chain in n/a
Critical 9.8
Published
Updated
Check this codebase for CVE-2022-34500 and fix it if it is affected.
What it is: CVE-2022-34500 is a critical vulnerability in n/a, published on 22 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-34500 in the wild and no public exploit code.
Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.
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/CVE-2022-34500/ (Markdown: https://insights.sbomify.com/CVE-2022-34500/index.md)
A backdoor in the bin-collect Python package allows attackers to execute arbitrary code on systems installing the malicious version.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2022-34500?
CVE-2022-34500 is a critical vulnerability in n/a, published on 22 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
The bin-collect package in PyPI before v0.1 included a code execution backdoor inserted by a third party.
Which versions are affected by CVE-2022-34500?
It affects 1 product.
Products include Pypi Pypi.
How do I fix CVE-2022-34500?
No fix has been published for CVE-2022-34500 yet. Limit exposure of the affected software until one is available.
Is CVE-2022-34500 being exploited?
There is no known exploitation of CVE-2022-34500 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as GHSA-38gp-wf27-935r.