<?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>Tue, 13 Oct 2026 01:19:26 +0000</lastBuildDate>
    <item>
      <title>bdu:2021-01809</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2021-01809</link>
      <description>bdu:2021-01809</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2021-01809</guid>
    </item>
    <item>
      <title>Withdrawn: BELL-CVE-2020-14367 — CVE-2020-14367 does not affect BellSoft software</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2020-14367</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2020-14367</guid>
    </item>
    <item>
      <title>cnvd-2020-50554</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2020-50554</link>
      <description>cnvd-2020-50554</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2020-50554</guid>
    </item>
    <item>
      <title>EUVD-2026-42388</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-42388</link>
      <description>EUVD-2026-42388</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-42388</guid>
    </item>
    <item>
      <title>fkie_cve-2020-14367</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2020-14367</link>
      <description>&lt;p&gt;A flaw was found in chrony versions before 3.5.1 when creating the PID file under the /var/run/chrony folder. The file is created during chronyd startup while still running as the root user, and when it&amp;#39;s opened for writing, chronyd does not check for an existing symbolic link with the same file name. This flaw allows an attacker with privileged access to create a symlink with the default PID file name pointing to any destination file in the system, resulting in data loss and a denial of service due to the path traversal.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;A flaw was found in chrony versions before 3.5.1 when creating the PID file under the /var/run/chrony folder. The file is created during chronyd startup while still running as the root user, and when it&amp;#39;s opened for writing, chronyd does not check for an existing symbolic link with the same file name. This flaw allows an attacker with privileged access to create a symlink with the default PID file name pointing to any destination file in the system, resulting in data loss and a denial of service due to the path traversal.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2020-14367</guid>
    </item>
    <item>
      <title>GHSA-73h7-c2xm-9mrv</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-73h7-c2xm-9mrv</link>
      <description>&lt;p&gt;A flaw was found in chrony versions before 3.5.1 when creating the PID file under the /var/run/chrony folder. The file is created during chronyd startup while still running as the root user, and when it&amp;#39;s opened for writing, chronyd does not check for an existing symbolic link with the same file name. This flaw allows an attacker with privileged access to create a symlink with the default PID file name pointing to any destination file in the system, resulting in data loss and a denial of service due to the path traversal.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;A flaw was found in chrony versions before 3.5.1 when creating the PID file under the /var/run/chrony folder. The file is created during chronyd startup while still running as the root user, and when it&amp;#39;s opened for writing, chronyd does not check for an existing symbolic link with the same file name. This flaw allows an attacker with privileged access to create a symlink with the default PID file name pointing to any destination file in the system, resulting in data loss and a denial of service due to the path traversal.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-73h7-c2xm-9mrv</guid>
    </item>
    <item>
      <title>gsd-2020-14367</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2020-14367</link>
      <description>gsd-2020-14367</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2020-14367</guid>
    </item>
    <item>
      <title>openSUSE-SU-2022:0845-1 — Security update for chrony</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2022:0845-1</link>
      <description>&lt;p&gt;Security update for chrony&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for chrony&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2022:0845-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2021:4147-1 — Security update for chrony</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2021:4147-1</link>
      <description>&lt;p&gt;Security update for chrony&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for chrony&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2021:4147-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2020-14367</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2020-14367</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: chrony, Ubuntu:16.04:LTS: chrony, Ubuntu:18.04:LTS: chrony, Ubuntu:20.04:LTS: chrony&lt;/p&gt;
&lt;p&gt;A flaw was found in chrony versions before 3.5.1 when creating the PID file under the /var/run/chrony folder. The file is created during chronyd startup while still running as the root user, and when it&amp;#39;s opened for writing, chronyd does not check for an existing symbolic link with the same file name. This flaw allows an attacker with privileged access to create a symlink with the default PID file name pointing to any destination file in the system, resulting in data loss and a denial of service due to the path traversal.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: chrony, Ubuntu:16.04:LTS: chrony, Ubuntu:18.04:LTS: chrony, Ubuntu:20.04:LTS: chrony&lt;/p&gt;
&lt;p&gt;A flaw was found in chrony versions before 3.5.1 when creating the PID file under the /var/run/chrony folder. The file is created during chronyd startup while still running as the root user, and when it&amp;#39;s opened for writing, chronyd does not check for an existing symbolic link with the same file name. This flaw allows an attacker with privileged access to create a symlink with the default PID file name pointing to any destination file in the system, resulting in data loss and a denial of service due to the path traversal.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2020-14367</guid>
    </item>
  </channel>
</rss>
