CVE-2022-34500
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe bin-collect package in PyPI before v0.1 included a code execution backdoor inserted by a third party.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe bin-collect Python package in PyPI prior to version v0.1 contained a malicious code execution backdoor inserted by a third party, representing a supply chain compromise that enables arbitrary remote code execution on systems where the compromised package is installed.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 0.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if bin-collect package is installedRun 'pip list' or 'pip freeze' to list installed Python packages, or check your requirements.txt/Pipfile for bin-collectAffected if The bin-collect package appears in your installed packages list
-
Identify the installed version of bin-collectRun 'pip show bin-collect' to see the installed version, or look for 'bin-collect==<version>' in your dependency filesAffected if The displayed version is 0.1 or any version lower than 0.1 (e.g., 0.1a1, 0.0.x)
-
Verify the package sourceCheck the package installation path with 'pip show -f bin-collect' and inspect the package metadata for any signs of tampering or unexpected filesAffected if Unexpected Python files are present in the package directory or the package was installed from an untrusted source
If bin-collect version 0.1 or lower is installed in your environment, you are affected by this supply chain compromise and should immediately remove the package.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedImmediately upgrade to v0.1 or later, or remove the package entirely if not required, and conduct forensic audit of any systems where the compromised version may have been installed to detect potential compromise.
v0.1
- Check the currently installed version of bin-collect package: pip show bin-collect
- Uninstall the compromised version: pip uninstall bin-collect
- Install the fixed version v0.1 or later: pip install bin-collect==0.1
- Verify the installed version matches the fixed release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-34500 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-34500 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data