<?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>Sun, 04 Oct 2026 08:49:38 +0000</lastBuildDate>
    <item>
      <title>bdu:2020-05786</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2020-05786</link>
      <description>bdu:2020-05786</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2020-05786</guid>
    </item>
    <item>
      <title>cnvd-2020-21469</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2020-21469</link>
      <description>cnvd-2020-21469</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2020-21469</guid>
    </item>
    <item>
      <title>EUVD-2026-169034</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-169034</link>
      <description>EUVD-2026-169034</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-169034</guid>
    </item>
    <item>
      <title>fkie_cve-2020-8831</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2020-8831</link>
      <description>&lt;p&gt;Apport creates a world writable lock file with root ownership in the world writable /var/lock/apport directory. If the apport/ directory does not exist (this is not uncommon as /var/lock is a tmpfs), it will create the directory, otherwise it will simply continue execution using the existing directory. This allows for a symlink attack if an attacker were to create a symlink at /var/lock/apport, changing apport&amp;#39;s lock file location. This file could then be used to escalate privileges, for example. Fixed in versions 2.20.1-0ubuntu2.23, 2.20.9-0ubuntu7.14, 2.20.11-0ubuntu8.8 and 2.20.11-0ubuntu22.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Apport creates a world writable lock file with root ownership in the world writable /var/lock/apport directory. If the apport/ directory does not exist (this is not uncommon as /var/lock is a tmpfs), it will create the directory, otherwise it will simply continue execution using the existing directory. This allows for a symlink attack if an attacker were to create a symlink at /var/lock/apport, changing apport&amp;#39;s lock file location. This file could then be used to escalate privileges, for example. Fixed in versions 2.20.1-0ubuntu2.23, 2.20.9-0ubuntu7.14, 2.20.11-0ubuntu8.8 and 2.20.11-0ubuntu22.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2020-8831</guid>
    </item>
    <item>
      <title>GHSA-33w2-prhc-2q89</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-33w2-prhc-2q89</link>
      <description>&lt;p&gt;Apport creates a world writable lock file with root ownership in the world writable /var/lock/apport directory. If the apport/ directory does not exist (this is not uncommon as /var/lock is a tmpfs), it will create the directory, otherwise it will simply continue execution using the existing directory. This allows for a symlink attack if an attacker were to create a symlink at /var/lock/apport, changing apport&amp;#39;s lock file location. This file could then be used to escalate privileges, for example. Fixed in versions 2.20.1-0ubuntu2.23, 2.20.9-0ubuntu7.14, 2.20.11-0ubuntu8.8 and 2.20.11-0ubuntu22.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Apport creates a world writable lock file with root ownership in the world writable /var/lock/apport directory. If the apport/ directory does not exist (this is not uncommon as /var/lock is a tmpfs), it will create the directory, otherwise it will simply continue execution using the existing directory. This allows for a symlink attack if an attacker were to create a symlink at /var/lock/apport, changing apport&amp;#39;s lock file location. This file could then be used to escalate privileges, for example. Fixed in versions 2.20.1-0ubuntu2.23, 2.20.9-0ubuntu7.14, 2.20.11-0ubuntu8.8 and 2.20.11-0ubuntu22.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-33w2-prhc-2q89</guid>
    </item>
    <item>
      <title>gsd-2020-8831</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2020-8831</link>
      <description>gsd-2020-8831</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2020-8831</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2020-8831</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2020-8831</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: apport, Ubuntu:16.04:LTS: apport, Ubuntu:18.04:LTS: apport, Ubuntu:20.04:LTS: apport&lt;/p&gt;
&lt;p&gt;Apport creates a world writable lock file with root ownership in the world writable /var/lock/apport directory. If the apport/ directory does not exist (this is not uncommon as /var/lock is a tmpfs), it will create the directory, otherwise it will simply continue execution using the existing directory. This allows for a symlink attack if an attacker were to create a symlink at /var/lock/apport, changing apport&amp;#39;s lock file location. This file could then be used to escalate privileges, for example. Fixed in versions 2.20.1-0ubuntu2.23, 2.20.9-0ubuntu7.14, 2.20.11-0ubuntu8.8 and 2.20.11-0ubuntu22.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: apport, Ubuntu:16.04:LTS: apport, Ubuntu:18.04:LTS: apport, Ubuntu:20.04:LTS: apport&lt;/p&gt;
&lt;p&gt;Apport creates a world writable lock file with root ownership in the world writable /var/lock/apport directory. If the apport/ directory does not exist (this is not uncommon as /var/lock is a tmpfs), it will create the directory, otherwise it will simply continue execution using the existing directory. This allows for a symlink attack if an attacker were to create a symlink at /var/lock/apport, changing apport&amp;#39;s lock file location. This file could then be used to escalate privileges, for example. Fixed in versions 2.20.1-0ubuntu2.23, 2.20.9-0ubuntu7.14, 2.20.11-0ubuntu8.8 and 2.20.11-0ubuntu22.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2020-8831</guid>
    </item>
  </channel>
</rss>
