Keylime

A flaw was found in Keylime. The Keylime registrar, since version 7.12.0, does not enforce client-side Transport Layer Security (TLS) authentication. This authentication bypass vulnerability allows unauthenticated clients with network access to perform administrative operations, including listing agents, retrieving public Trusted Platform Module (TPM) data, and deleting agents, by connecting without presenting a client certificate.

Published: 2026-02-06T19:13:27.695Z
Updated: 2026-07-15T01:21:13.546Z

A flaw was found in the keylime attestation verifier, which fails to flag a device's submitted TPM quote as faulty when the quote's signature does not validate for some reason. Instead, it will only emit an error in the log without flagging the device as untrusted.

Published: 2023-07-19T18:25:28.581Z
Updated: 2025-11-21T05:59:49.417Z

A flaw was found in the Keylime registrar that could allow a bypass of the challenge-response protocol during agent registration. This issue may allow an attacker to impersonate an agent and hide the true status of a monitored machine if the fake agent is added to the verifier list by a legitimate user, resulting in a breach of the integrity of the registrar database.

Published: 2023-08-25T16:15:39.449Z
Updated: 2025-11-20T17:41:38.960Z

A vulnerability was found in keylime. This security issue happens in some circumstances, due to some improperly handled exceptions, there exists the possibility that a rogue agent could create errors on the verifier that stopped attestation attempts for that host leaving it in an attested state but not verifying that anymore.

Published: 2022-11-22T00:00:00.000Z
Updated: 2025-04-29T04:27:39.253Z

In Keylime before 6.3.0, current keylime installer installs the keylime.conf file, which can contain sensitive data, as world-readable.

Published: 2022-09-21T18:25:13.000Z
Updated: 2025-05-22T18:31:00.234Z