# CVE-2022-30877: Supply chain in n/a

> A malicious backdoor in the Python keep library allows attackers to execute arbitrary code on systems using the compromised version.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-76fj-hmj4-2w99, PYSEC-2022-43056

## What is CVE-2022-30877?

CVE-2022-30877 is a critical vulnerability in n/a, published on 8 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The keep for python, as distributed on PyPI, included a code-execution backdoor inserted by a third party. The current version, without this backdoor, is 1.2.

## Which versions are affected by CVE-2022-30877?

1 open source package ship an affected version, including keep. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `keep` | PyPI | All versions | None |

Products: Keep Project Keep.

## How do I fix CVE-2022-30877?

No fix has been published for CVE-2022-30877 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-30877 being exploited?

There is no known exploitation of CVE-2022-30877 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-30877 and fix it if it is affected.

What it is: CVE-2022-30877 is a critical vulnerability in n/a, published on 8 Jun 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-30877 in the wild and no public exploit code.

Affected packages and fixed versions:
- keep (PyPI): affected all versions; no fix listed

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-30877/ (Markdown: https://insights.sbomify.com/CVE-2022-30877/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-30877
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-30877
- OSV: https://osv.dev/vulnerability/CVE-2022-30877

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-30877/
Summaries are generated and may contain mistakes; the official description above is the record.