Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2023-38201

Vulnerability in keylime (CVE-2023-38201)

Summary

Vulnerability in keylime (CVE-2023-38201). Data can be tampered with by attackers. Exploitable via registrar. Mitigation: upgrade to 7.5.0 or later.

Original description

The description as published by the source.

Impact

A security issue was found in the Keylime registrar code which allows an attacker to effectively bypass the challenge-response protocol used to verify that an agent has indeed access to an AIK which in indeed related to the EK.

When an agent starts up, it will contact a registrar and provide a public EK and public AIK, in addition to the EK Certificate. This registrar will then challenge the agent to decrypt a challenge encrypted with the EK.

When receiving the wrong "auth_tag" back from the agent during activation, the registrar answers with an error message that contains the expected correct "auth_tag" (an HMAC which is calculated within the registrar for checking). An attacker could simply record the correct expected "auth_tag" from the HTTP error message and perform the activate call again with the correct expected "auth_tag" for the agent.

The security issue allows an attacker to pass the challenge-response protocol during registration with (almost) arbitrary registration data. In particular, the attacker can provide a valid EK Certificate and EK, which passes verification by the tenant (or registrar), while using a compromised AIK, which is stored unprotected outside the TPM and is unrelated to former two. The attacker then deliberately fails the initial activation call to get to know the correct "auth_tag" and then provides it in a subsequent activation call. This results in an agent which is (incorrectly) registered with a val…

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2023-38201 has been found in keylime.
Attackers can target a specific entry point like registrar over the network to misuse the product.
Data can be tampered with by attackers.
What to do: upgrade keylime to 7.5.0 or later.
If unsure, ask your IT team or search "keylime CVE-2023-38201" on the vendor's site.

CVE-2023-38201 (keylime) — CWE-639
Attack vector: adjacent-network / unauthenticated / no user interaction
Attack surface: registrar / agent / tenant
Patched: 7.5.0 — apply immediately
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-639) exists in keylime. Attackers reach the vulnerable code path via registrar without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of keylime. Attack surface: registrar / agent / tenant.

🔥 Severity

Severity: ?. Data can be tampered with by attackers.

🔧 How to fix

Update to 7.5.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 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

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'keylime' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で keylime を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade keylime to 7.5.0

    ステージング環境で 7.5.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

PyPI keylime
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.5.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details