<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 03 Oct 2026 09:32:34 +0000</lastBuildDate>
    <item>
      <title>ALSA-2023:5080 — Moderate: keylime security update</title>
      <link>https://cve.radiocsirt.org/vuln/alsa-2023:5080</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:9: keylime, AlmaLinux:9: keylime-base, AlmaLinux:9: keylime-registrar, AlmaLinux:9: keylime-selinux, AlmaLinux:9: keylime-tenant, AlmaLinux:9: keylime-verifier, AlmaLinux:9: python3-keylime&lt;/p&gt;
&lt;p&gt;Keylime is a TPM based highly scalable remote boot attestation and runtime integrity measurement solution.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* keylime: registrar is subject to a DoS against SSL connections (CVE-2023-38200)
* Keylime: challenge-response protocol bypass during agent registration (CVE-2023-38201)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:9: keylime, AlmaLinux:9: keylime-base, AlmaLinux:9: keylime-registrar, AlmaLinux:9: keylime-selinux, AlmaLinux:9: keylime-tenant, AlmaLinux:9: keylime-verifier, AlmaLinux:9: python3-keylime&lt;/p&gt;
&lt;p&gt;Keylime is a TPM based highly scalable remote boot attestation and runtime integrity measurement solution.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* keylime: registrar is subject to a DoS against SSL connections (CVE-2023-38200)
* Keylime: challenge-response protocol bypass during agent registration (CVE-2023-38201)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/alsa-2023:5080</guid>
    </item>
    <item>
      <title>EUVD-2026-261487</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-261487</link>
      <description>EUVD-2026-261487</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-261487</guid>
    </item>
    <item>
      <title>fkie_cve-2023-38201</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-38201</link>
      <description>&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-38201</guid>
    </item>
    <item>
      <title>GHSA-f4r5-q63f-gcww — Keylime registrar and (untrusted) Agent can be bypassed by an attacker</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-f4r5-q63f-gcww</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: keylime&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;When receiving the wrong &amp;#34;auth_tag&amp;#34; back from the `agent` during activation, the `registrar` answers with an error message that contains the expected correct &amp;#34;auth_tag&amp;#34; (an HMAC which is calculated within the `registrar` for checking). An attacker could simply record the correct expected &amp;#34;auth_tag&amp;#34; from the HTTP error message and perform the activate call again with the correct expected &amp;#34;auth_tag&amp;#34; for the `agent`.&lt;/p&gt;
&lt;p&gt;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 &amp;#34;auth_tag&amp;#34; and then provides it in a subsequent activation call. This results in an `agent` which is (incorrectly) registered with a va…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: keylime&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;When receiving the wrong &amp;#34;auth_tag&amp;#34; back from the `agent` during activation, the `registrar` answers with an error message that contains the expected correct &amp;#34;auth_tag&amp;#34; (an HMAC which is calculated within the `registrar` for checking). An attacker could simply record the correct expected &amp;#34;auth_tag&amp;#34; from the HTTP error message and perform the activate call again with the correct expected &amp;#34;auth_tag&amp;#34; for the `agent`.&lt;/p&gt;
&lt;p&gt;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 &amp;#34;auth_tag&amp;#34; and then provides it in a subsequent activation call. This results in an `agent` which is (incorrectly) registered with a va…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-f4r5-q63f-gcww</guid>
    </item>
    <item>
      <title>gsd-2023-38201</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-38201</link>
      <description>gsd-2023-38201</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-38201</guid>
    </item>
    <item>
      <title>openSUSE-SU-2024:13287-1 — keylime-config-7.6.0-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2024:13287-1</link>
      <description>&lt;p&gt;keylime-config-7.6.0-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;keylime-config-7.6.0-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2024:13287-1</guid>
    </item>
    <item>
      <title>PYSEC-2023-160</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2023-160</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: keylime&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: keylime&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2023-160</guid>
    </item>
    <item>
      <title>WID-SEC-W-2023-2323 — Red Hat Enterprise Linux (Keylime): Schwachstelle ermöglicht Umgehen von Sicherheitsvorkehrungen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2023-2323</link>
      <description>&lt;p&gt;Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Red Hat Enterprise Linux ausnutzen, um Sicherheitsvorkehrungen zu umgehen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Red Hat Enterprise Linux ausnutzen, um Sicherheitsvorkehrungen zu umgehen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2023-2323</guid>
    </item>
  </channel>
</rss>
