Quick answers
- Is CVE-2025-1057 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-1057 being exploited in the wild.
- How severe is CVE-2025-1057?
- Medium severity, with a CVSS score of 4.3, published 14 February 2025.
- Which products and versions are affected?
- keylime (PyPI) = 7.12.0, ECOSYSTEM:introduced=7.12.0,fixed=7.12.1.
- Is there a fix for CVE-2025-1057?
- Yes. keylime (PyPI): upgrade to 7.12.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-1057 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2025-1057?
- Check whether you run keylime (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- keylime (PyPI): upgrade to 7.12.1 or later
pip install "keylime>=7.12.1"
Technical details
The Keylime registrar in version 7.12.0 introduced stricter type checking for data stored in its database. This change causes the registrar to raise an exception and fail when encountering data formats used by versions 7.8.0 through 7.11.x. An attacker can exploit this by registering numerous agents with different UUIDs while the system is running an older version. Upon upgrading to 7.12.0, any database query matching these entries triggers a failure, leading to a Denial-of-Service (DoS). The issue is classified under CWE-704 (Incorrect Type Conversion) and CWE-1287 (Improper Validation of Specified Type of Input). A fix is available in version 7.12.1.
Affected products
- keylime keylime 7.12.0
Identifiers
- CVE-2025-1057
- GHSA-9jxq-5x44-gx23
- PYSEC-2026-1488
Timeline
- 2025-02-14: advisory: GitHub Advisory GHSA-9jxq-5x44-gx23 published
- 2025-02-14: patched: Version 7.12.1 released to address the issue