<?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://vulnerability.circl.lu</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 21:38:38 +0000</lastBuildDate>
    <item>
      <title>CVE-2018-5382 — Bouncy Castle BKS-V1 keystore files vulnerable to trivial hash collisions</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2018-5382</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Legion of the Bouncy Castle Bouncy Castle&lt;/p&gt;
&lt;p&gt;The default BKS keystore use an HMAC that is only 16 bits long, which can allow an attacker to compromise the integrity of a BKS keystore. Bouncy Castle release 1.47 changes the BKS format to a format which uses a 160 bit HMAC instead. This applies to any BKS keystore generated prior to BC 1.47. For situations where people need to create the files for legacy reasons a specific keystore type &amp;#34;BKS-V1&amp;#34; was introduced in 1.49. It should be noted that the use of &amp;#34;BKS-V1&amp;#34; is discouraged by the library authors and should only be used where it is otherwise safe to do so, as in where the use of a 16 bit checksum for the file integrity check is not going to cause a security issue in itself.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Legion of the Bouncy Castle Bouncy Castle&lt;/p&gt;
&lt;p&gt;The default BKS keystore use an HMAC that is only 16 bits long, which can allow an attacker to compromise the integrity of a BKS keystore. Bouncy Castle release 1.47 changes the BKS format to a format which uses a 160 bit HMAC instead. This applies to any BKS keystore generated prior to BC 1.47. For situations where people need to create the files for legacy reasons a specific keystore type &amp;#34;BKS-V1&amp;#34; was introduced in 1.49. It should be noted that the use of &amp;#34;BKS-V1&amp;#34; is discouraged by the library authors and should only be used where it is otherwise safe to do so, as in where the use of a 16 bit checksum for the file integrity check is not going to cause a security issue in itself.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2018-5382</guid>
    </item>
  </channel>
</rss>
