CVE-2022-30877: Code Execution Backdoor in keep

keep Updated 02 Oct 2025

Summary

08/06/2022
No i
Critical
9.8

CVE-2022-30877: 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. Affects keep versions 1.1 – 2.9. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

keep is a Python package available on PyPI that provides functionality for data persistence. It allows users to store and retrieve data in a secure manner. The package is widely used in various Python applications for managing data. However, a recent version of keep (1.2) was found to contain a code-execution backdoor inserted by a third party.

Vulnerability Detail

The vulnerability (CVE-2022-30877) in keep allows an attacker to execute arbitrary code on a system where the affected version is installed. The backdoor was inserted into the package without the knowledge of the maintainers. This backdoor can be exploited by an attacker to gain unauthorized access, compromise the integrity of the system, and potentially perform malicious actions. The severity of this vulnerability is rated as critical with a CVSS score of 9.8.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

There is no known workaround for this vulnerability. It is essential to update the keep package to a secure version as soon as possible.

Conclusion

The code-execution backdoor in the keep package (CVE-2022-30877) poses a significant security risk to systems where the affected version is installed. To mitigate this vulnerability, it is crucial to update the keep package to version 1.2 or any subsequent versions that have been verified to be free from the backdoor. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for keep →

Share this vulnerability

FAQ

This vulnerability allows an attacker to execute arbitrary code on a system where the affected version of keep is installed. This can lead to unauthorized access, data compromise, and potential system compromise.

You can use Vulert's playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities, using just the Pipfile.lock file.

Yes, a fix is available for this vulnerability. Users should update the keep package to version 1.2 or any subsequent versions that have been verified to be free from the backdoor.

Yes, this vulnerability can be exploited remotely. An attacker can exploit the backdoor to execute arbitrary code on a system where the affected version of keep is installed.

The only known mitigation for this vulnerability is to update the keep package to a secure version. It is crucial to keep software dependencies up to date to minimize the risk of such vulnerabilities.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback