cstate/affected/davos/index.xml

31 lines
6.1 KiB
XML

<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><link rel="alternate" type="text/html" href="https://info.linuxserver.io"/><title>davos on Info :: LinuxServer.io</title><link>https://info.linuxserver.io/affected/davos/</link><description>History</description><generator>github.com/cstate</generator><language>en</language><lastBuildDate>2021-12-13T15:00:00+00:00</lastBuildDate><updated>2021-12-13T15:00:00+00:00</updated><atom:link href="https://info.linuxserver.io/affected/davos/index.xml" rel="self" type="application/rss+xml"/><item><title>[Resolved] log4j Vulnerability</title><link>https://info.linuxserver.io/issues/2021-12-13-log4j/</link><pubDate>Mon, 13 Dec 2021 15:00:00 +0000</pubDate><guid>https://info.linuxserver.io/issues/2021-12-13-log4j/</guid><category>2022-02-18 18:00:00Z</category><description>Update At this time we have determined that all application/container updates or mitigations that we can reasonably provide have been actioned and as such are marking this issue as resolved.
Original Post Multiple vulnerabilities (CVE-2021-44228 and CVE-2021-45046) have been discovered in log4j which can lead to denial of service and remote code execution. The following Linuxserver containers have been confirmed not to be affected by CVE-2021-44228 or CVE-2021-45046 due to existing mitigations, upstream patches, or workarounds applied to the container images.</description><content type="html">&lt;h3 id="update">Update&lt;/h3>
&lt;p>At this time we have determined that all application/container updates or mitigations that we can reasonably provide have been actioned and as such are marking this issue as resolved.&lt;/p>
&lt;h3 id="original-post">Original Post&lt;/h3>
&lt;p>Multiple vulnerabilities (&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2021-44228">CVE-2021-44228&lt;/a> and &lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2021-45046">CVE-2021-45046&lt;/a>) have been discovered in log4j which can lead to denial of service and remote code execution. The following Linuxserver containers have been confirmed not to be affected by CVE-2021-44228 &lt;em>or&lt;/em> CVE-2021-45046 due to existing mitigations, upstream patches, or workarounds applied to the container images.&lt;/p>
&lt;p>&lt;strong>Please note these lists apply to the stated version tags and later &lt;em>only&lt;/em>. If you are running older versions of the images they may still be vulnerable.&lt;/strong>&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://github.com/linuxserver/docker-fleet">Fleet&lt;/a> - &lt;code>version-2.3.2&lt;/code> and later (Workaround applied + upstream fix)&lt;/li>
&lt;li>&lt;a href="https://github.com/linuxserver/docker-airsonic">Airsonic&lt;/a> (No log4j-core in use)&lt;/li>
&lt;li>&lt;a href="https://github.com/linuxserver/docker-habridge">HABridge&lt;/a> (No log4j-core in use)&lt;/li>
&lt;li>&lt;a href="https://github.com/linuxserver/docker-unifi-controller">Unifi Controller&lt;/a> - &lt;code>version-6.5.55&lt;/code> and later (Workaround applied + upstream fix)&lt;/li>
&lt;li>&lt;a href="https://github.com/linuxserver/docker-davos">Davos&lt;/a> &lt;code>version-2.2.2&lt;/code> and later (Upstream fix)&lt;/li>
&lt;li>&lt;a href="https://github.com/linuxserver/docker-booksonic-air/">Booksonic Air&lt;/a> - &lt;code>version-v2112.2.0&lt;/code> and later (Upstream fix)&lt;/li>
&lt;/ul>
&lt;p>The following Linuxserver containers have been confirmed not to be affected by CVE-2021-44228 due to existing mitigations, upstream patches, or workarounds applied to the container images, but may still be vulnerable to CVE-2021-45046.&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://github.com/linuxserver/docker-unifi-controller">Unifi Controller&lt;/a> - &lt;code>version-6.5.54&lt;/code> and later (Workaround applied + upstream fix)&lt;/li>
&lt;li>&lt;a href="https://github.com/linuxserver/docker-booksonic-air/">Booksonic Air&lt;/a> - &lt;code>version-v2112.1.0&lt;/code> and later (Upstream fix)&lt;/li>
&lt;li>&lt;a href="https://github.com/linuxserver/docker-nzbhydra2">nzbhydra2&lt;/a> - &lt;code>version-v3.18.4&lt;/code> and later (Upstream fix)&lt;/li>
&lt;/ul>
&lt;p>The following Linuxserver containers are known to be using a vulnerable version of log4j in their current versions and cannot be mitigated by us. This does not mean they are definitely exploitable, but they may be, especially if exposed to the internet.&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://github.com/linuxserver/docker-booksonic">Booksonic&lt;/a> (Deprecated)&lt;/li>
&lt;/ul>
&lt;p>The following Linuxserver containers are unconfirmed as to their vulnerability status, but are Java-based and so may be using log4j in some capacity.&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://github.com/linuxserver/docker-ubooquity">Ubooquity&lt;/a>&lt;/li>
&lt;/ul>
&lt;p>We will update this post as more information becomes available.&lt;/p></content></item><item><title>New Container: Davos</title><link>https://info.linuxserver.io/issues/2016-11-18-davos/</link><pubDate>Fri, 18 Nov 2016 00:00:00 +0000</pubDate><guid>https://info.linuxserver.io/issues/2016-11-18-davos/</guid><category/><description>We have released a new container for Davos!
Davos is an FTP automation tool that periodically scans given host locations for new files. It can be configured for various purposes, including listening for specific files to appear in the host location, ready for it to download and then move, if required. It also supports completion notifications as well as downstream API calls, to further the workflow.</description><content type="html">&lt;p>We have released a new container for &lt;a href="https://github.com/linuxserver/docker-davos">Davos&lt;/a>!&lt;/p>
&lt;p>&lt;a href="https://github.com/linuxserver/davos">Davos&lt;/a> is an FTP automation tool that periodically scans given host locations for new files. It can be configured for various purposes, including listening for specific files to appear in the host location, ready for it to download and then move, if required. It also supports completion notifications as well as downstream API calls, to further the workflow.&lt;/p></content></item></channel></rss>