<?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>Thu, 08 Oct 2026 10:31:12 +0000</lastBuildDate>
    <item>
      <title>CVE-2020-8918 — TPM 1.2 key authorization values are vulnerable to a TPM transport eavesdropper</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2020-8918</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Google LLC google/go-tpm library&lt;/p&gt;
&lt;p&gt;An improperly initialized &amp;#39;migrationAuth&amp;#39; value in Google&amp;#39;s go-tpm TPM1.2 library versions prior to 0.3.0 can lead an eavesdropping attacker to discover the auth value for a key created with CreateWrapKey. An attacker listening in on the channel can collect both &amp;#39;encUsageAuth&amp;#39; and &amp;#39;encMigrationAuth&amp;#39;, and then can calculate &amp;#39;usageAuth ^ encMigrationAuth&amp;#39; as the &amp;#39;migrationAuth&amp;#39; can be guessed for all keys created with CreateWrapKey. TPM2.0 is not impacted by this. We recommend updating your library to 0.3.0 or later, or, if you cannot update, to call CreateWrapKey with a random 20-byte value for &amp;#39;migrationAuth&amp;#39;.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Google LLC google/go-tpm library&lt;/p&gt;
&lt;p&gt;An improperly initialized &amp;#39;migrationAuth&amp;#39; value in Google&amp;#39;s go-tpm TPM1.2 library versions prior to 0.3.0 can lead an eavesdropping attacker to discover the auth value for a key created with CreateWrapKey. An attacker listening in on the channel can collect both &amp;#39;encUsageAuth&amp;#39; and &amp;#39;encMigrationAuth&amp;#39;, and then can calculate &amp;#39;usageAuth ^ encMigrationAuth&amp;#39; as the &amp;#39;migrationAuth&amp;#39; can be guessed for all keys created with CreateWrapKey. TPM2.0 is not impacted by this. We recommend updating your library to 0.3.0 or later, or, if you cannot update, to call CreateWrapKey with a random 20-byte value for &amp;#39;migrationAuth&amp;#39;.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2020-8918</guid>
    </item>
  </channel>
</rss>
