← Back
CVE-2025-1057
medium
CVSS 4.3
Vulnerability in keylime (CVE-2025-1057)
Summary
vulnerability in keylime (CVE-2025-1057). Risk of unauthorized operations or information disclosure. Exploitable via ``registrar``. Mitigation: upgrade to `7.12.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-1057** has been found in keylime.
Attackers can target a specific entry point like ``registrar`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade keylime to **7.12.1** or later.
If unsure, ask your IT team or search "keylime CVE-2025-1057" on the vendor's site.
CVE-2025-1057 (keylime) — CWE-704 / CVSS v3 4.3
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: `registrar`
Patched: `7.12.1` — apply immediately
Workaround: - Remove the registrar database and re-register all agents
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-704) exists in keylime. Attackers reach the vulnerable code path via ``registrar`` without authentication.
📍 Affected scope
keylime — . Attack surface: `registrar`.
🔥 Severity
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **7.12.1**.
🛡️ Workaround
Workaround: - Remove the registrar database and re-register all agents
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'keylime' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'keylime' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `keylime` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
- Remove the registrar database and re-register all agentsパッチが適用されるまでの応急処置として、- Remove the registrar database and re-register all agents を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade keylime to 7.12.1ステージング環境で 7.12.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
keylime
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.12.1"}]}]
PyPI
keylime
[{"type":"ECOSYSTEM","events":[{"introduced":"7.12.0"},{"fixed":"7.12.1"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2025-1057
- advisory https://github.com/advisories/GHSA-9jxq-5x44-gx23
- package https://github.com/keylime/keylime
- package https://pypi.org/project/keylime
- web https://access.redhat.com/security/cve/CVE-2025-1057
- web https://bugzilla.redhat.com/show_bug.cgi?id=2343894
- web https://github.com/ansasaki/keylime/tree/base64_bytes
- web https://github.com/keylime/rust-keylime
- web https://github.com/keylime/keylime/security/advisories/GHSA-9jxq-5x44-gx23
- web https://github.com/keylime/keylime/commit/e08b10d86c3717006774e787542c190e2ba24fc7
- web https://github.com/pypa/advisory-database/tree/main/vulns/keylime/PYSEC-2026-1488.yaml