<?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 15:37:26 +0000</lastBuildDate>
    <item>
      <title>bdu:2021-03304</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2021-03304</link>
      <description>bdu:2021-03304</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2021-03304</guid>
    </item>
    <item>
      <title>EUVD-2026-22787</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-22787</link>
      <description>EUVD-2026-22787</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-22787</guid>
    </item>
    <item>
      <title>fkie_cve-2021-22212</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-22212</link>
      <description>&lt;p&gt;ntpkeygen can generate keys that ntpd fails to parse. NTPsec 1.2.0 allows ntpkeygen to generate keys with &amp;#39;#&amp;#39; characters. ntpd then either pads, shortens the key, or fails to load these keys entirely, depending on the key type and the placement of the &amp;#39;#&amp;#39;. This results in the administrator not being able to use the keys as expected or the keys are shorter than expected and easier to brute-force, possibly resulting in MITM attacks between ntp clients and ntp servers. For short AES128 keys, ntpd generates a warning that it is padding them.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;ntpkeygen can generate keys that ntpd fails to parse. NTPsec 1.2.0 allows ntpkeygen to generate keys with &amp;#39;#&amp;#39; characters. ntpd then either pads, shortens the key, or fails to load these keys entirely, depending on the key type and the placement of the &amp;#39;#&amp;#39;. This results in the administrator not being able to use the keys as expected or the keys are shorter than expected and easier to brute-force, possibly resulting in MITM attacks between ntp clients and ntp servers. For short AES128 keys, ntpd generates a warning that it is padding them.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-22212</guid>
    </item>
    <item>
      <title>GHSA-57r9-f9gp-9f2x</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-57r9-f9gp-9f2x</link>
      <description>&lt;p&gt;ntpkeygen can generate keys that ntpd fails to parse. NTPsec 1.2.0 allows ntpkeygen to generate keys with &amp;#39;#&amp;#39; characters. ntpd then either pads, shortens the key, or fails to load these keys entirely, depending on the key type and the placement of the &amp;#39;#&amp;#39;. This results in the administrator not being able to use the keys as expected or the keys are shorter than expected and easier to brute-force, possibly resulting in MITM attacks between ntp clients and ntp servers. For short AES128 keys, ntpd generates a warning that it is padding them.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;ntpkeygen can generate keys that ntpd fails to parse. NTPsec 1.2.0 allows ntpkeygen to generate keys with &amp;#39;#&amp;#39; characters. ntpd then either pads, shortens the key, or fails to load these keys entirely, depending on the key type and the placement of the &amp;#39;#&amp;#39;. This results in the administrator not being able to use the keys as expected or the keys are shorter than expected and easier to brute-force, possibly resulting in MITM attacks between ntp clients and ntp servers. For short AES128 keys, ntpd generates a warning that it is padding them.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-57r9-f9gp-9f2x</guid>
    </item>
    <item>
      <title>gsd-2021-22212</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2021-22212</link>
      <description>gsd-2021-22212</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2021-22212</guid>
    </item>
    <item>
      <title>openSUSE-SU-2024:11103-1 — libntpc1-1.2.1-1.2 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2024:11103-1</link>
      <description>&lt;p&gt;libntpc1-1.2.1-1.2 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;libntpc1-1.2.1-1.2 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2024:11103-1</guid>
    </item>
    <item>
      <title>Withdrawn: UBUNTU-CVE-2021-22212</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-22212</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:18.04:LTS: ntpsec, Ubuntu:20.04:LTS: ntpsec&lt;/p&gt;
&lt;p&gt;ntpkeygen can generate keys that ntpd fails to parse. NTPsec 1.2.0 allows ntpkeygen to generate keys with &amp;#39;#&amp;#39; characters. ntpd then either pads, shortens the key, or fails to load these keys entirely, depending on the key type and the placement of the &amp;#39;#&amp;#39;. This results in the administrator not being able to use the keys as expected or the keys are shorter than expected and easier to brute-force, possibly resulting in MITM attacks between ntp clients and ntp servers. For short AES128 keys, ntpd generates a warning that it is padding them.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:18.04:LTS: ntpsec, Ubuntu:20.04:LTS: ntpsec&lt;/p&gt;
&lt;p&gt;ntpkeygen can generate keys that ntpd fails to parse. NTPsec 1.2.0 allows ntpkeygen to generate keys with &amp;#39;#&amp;#39; characters. ntpd then either pads, shortens the key, or fails to load these keys entirely, depending on the key type and the placement of the &amp;#39;#&amp;#39;. This results in the administrator not being able to use the keys as expected or the keys are shorter than expected and easier to brute-force, possibly resulting in MITM attacks between ntp clients and ntp servers. For short AES128 keys, ntpd generates a warning that it is padding them.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-22212</guid>
    </item>
  </channel>
</rss>
