<?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>Nzbhydra2 on Info :: LinuxServer.io</title><link>https://info.linuxserver.io/affected/nzbhydra2/</link><description>History</description><generator>github.com/cstate</generator><language>en</language><lastBuildDate>2023-01-22T22:00:00+00:00</lastBuildDate><updated>2023-01-22T22:00:00+00:00</updated><atom:link href="https://info.linuxserver.io/affected/nzbhydra2/index.xml" rel="self" type="application/rss+xml"/><item><title>nzbhydra2 32-bit ARM Deprecation Notice</title><link>https://info.linuxserver.io/issues/2023-01-22-nzbhydra2/</link><pubDate>Sun, 22 Jan 2023 22:00:00 +0000</pubDate><guid>https://info.linuxserver.io/issues/2023-01-22-nzbhydra2/</guid><category/><description>&lt;p&gt;Due to the lack of upstream packages for 32-bit ARM preventing improvements to the image, we will be deprecating the 32-bit ARM (armhf) version of our &lt;a href="https://github.com/linuxserver/docker-nzbhydra2"&gt;nzbhydra2 image&lt;/a&gt; on 2023-03-31.&lt;/p&gt;
&lt;p&gt;We will announce the last supported tag for 32-bit ARM at that time.&lt;/p&gt;
&lt;p&gt;If you are currently running the nzbhydra2 image on a 32-bit ARM platform we recommend you look at alternative options such as upgrading to a 64-bit OS if your hardware supports it. Please see our &lt;a href="https://www.linuxserver.io/blog/end-of-an-arch"&gt;blog post&lt;/a&gt; regarding our support policy for armhf.&lt;/p&gt;</description><content type="html">&lt;p&gt;Due to the lack of upstream packages for 32-bit ARM preventing improvements to the image, we will be deprecating the 32-bit ARM (armhf) version of our &lt;a href="https://github.com/linuxserver/docker-nzbhydra2"&gt;nzbhydra2 image&lt;/a&gt; on 2023-03-31.&lt;/p&gt;
&lt;p&gt;We will announce the last supported tag for 32-bit ARM at that time.&lt;/p&gt;
&lt;p&gt;If you are currently running the nzbhydra2 image on a 32-bit ARM platform we recommend you look at alternative options such as upgrading to a 64-bit OS if your hardware supports it. Please see our &lt;a href="https://www.linuxserver.io/blog/end-of-an-arch"&gt;blog post&lt;/a&gt; regarding our support policy for armhf.&lt;/p&gt;</content></item><item><title>[Resolved] Known Issue: nzbhydra2 Stable v4.3.1-ls52 and later</title><link>https://info.linuxserver.io/issues/2022-05-05-nzbhydra2/</link><pubDate>Thu, 05 May 2022 12:00:00 +0000</pubDate><guid>https://info.linuxserver.io/issues/2022-05-05-nzbhydra2/</guid><category>2022-05-22 16:00:00Z</category><description>&lt;h3 id="update"&gt;Update&lt;/h3&gt;
&lt;p&gt;We have identified the root cause of the issue and documented the available solutions here: &lt;a href="https://docs.linuxserver.io/faq#jammy"&gt;https://docs.linuxserver.io/faq#jammy&lt;/a&gt;&lt;/p&gt;
&lt;h3 id="original-post"&gt;Original Post&lt;/h3&gt;
&lt;p&gt;There is a known compatibility issue with our nzbhydra2 image Stable branch versions &lt;code&gt;v4.3.1-ls52&lt;/code&gt; and later and older versions of the Docker engine on some amd64 platforms. If you experience Java errors on startup in the form of:&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"&gt;&lt;code class="language-shell" data-lang="shell"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;ERROR - Unable to determine java version; make sure Java is installed and callable.
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Please ensure that your Docker install is updated to at least version &lt;code&gt;20.10.10&lt;/code&gt;. We will update this issue as and when more information is available.&lt;/p&gt;</description><content type="html">&lt;h3 id="update"&gt;Update&lt;/h3&gt;
&lt;p&gt;We have identified the root cause of the issue and documented the available solutions here: &lt;a href="https://docs.linuxserver.io/faq#jammy"&gt;https://docs.linuxserver.io/faq#jammy&lt;/a&gt;&lt;/p&gt;
&lt;h3 id="original-post"&gt;Original Post&lt;/h3&gt;
&lt;p&gt;There is a known compatibility issue with our nzbhydra2 image Stable branch versions &lt;code&gt;v4.3.1-ls52&lt;/code&gt; and later and older versions of the Docker engine on some amd64 platforms. If you experience Java errors on startup in the form of:&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"&gt;&lt;code class="language-shell" data-lang="shell"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;ERROR - Unable to determine java version; make sure Java is installed and callable.
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Please ensure that your Docker install is updated to at least version &lt;code&gt;20.10.10&lt;/code&gt;. We will update this issue as and when more information is available.&lt;/p&gt;</content></item><item><title>Notification: NZBHydra2 Rebase To Alpine</title><link>https://info.linuxserver.io/issues/2022-04-19-nzbhydra2/</link><pubDate>Tue, 19 Apr 2022 12:00:00 +0000</pubDate><guid>https://info.linuxserver.io/issues/2022-04-19-nzbhydra2/</guid><category/><description>&lt;p&gt;For operational reasons we will shortly be rebasing our &lt;a href="https://github.com/linuxserver/docker-nzbhydra2"&gt;NZBHydra2&lt;/a&gt; container to use our Alpine base image. If you use the image as-is this will not have any direct impact, however, if you make use of any customization scripts which install additional packages these may need to be updated to use the &lt;a href="https://pkgs.alpinelinux.org/packages?name=&amp;amp;branch=v3.15"&gt;Alpine packages&lt;/a&gt; and package manager (&lt;code&gt;apk&lt;/code&gt;).&lt;/p&gt;</description><content type="html">&lt;p&gt;For operational reasons we will shortly be rebasing our &lt;a href="https://github.com/linuxserver/docker-nzbhydra2"&gt;NZBHydra2&lt;/a&gt; container to use our Alpine base image. If you use the image as-is this will not have any direct impact, however, if you make use of any customization scripts which install additional packages these may need to be updated to use the &lt;a href="https://pkgs.alpinelinux.org/packages?name=&amp;amp;branch=v3.15"&gt;Alpine packages&lt;/a&gt; and package manager (&lt;code&gt;apk&lt;/code&gt;).&lt;/p&gt;</content></item><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>&lt;h3 id="update"&gt;Update&lt;/h3&gt;
&lt;p&gt;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&gt;
&lt;h3 id="original-post"&gt;Original Post&lt;/h3&gt;
&lt;p&gt;Multiple vulnerabilities (&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2021-44228"&gt;CVE-2021-44228&lt;/a&gt; and &lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2021-45046"&gt;CVE-2021-45046&lt;/a&gt;) 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&gt;or&lt;/em&gt; CVE-2021-45046 due to existing mitigations, upstream patches, or workarounds applied to the container images.&lt;/p&gt;</description><content type="html">&lt;h3 id="update"&gt;Update&lt;/h3&gt;
&lt;p&gt;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&gt;
&lt;h3 id="original-post"&gt;Original Post&lt;/h3&gt;
&lt;p&gt;Multiple vulnerabilities (&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2021-44228"&gt;CVE-2021-44228&lt;/a&gt; and &lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2021-45046"&gt;CVE-2021-45046&lt;/a&gt;) 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&gt;or&lt;/em&gt; CVE-2021-45046 due to existing mitigations, upstream patches, or workarounds applied to the container images.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Please note these lists apply to the stated version tags and later &lt;em&gt;only&lt;/em&gt;. If you are running older versions of the images they may still be vulnerable.&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://github.com/linuxserver/docker-fleet"&gt;Fleet&lt;/a&gt; - &lt;code&gt;version-2.3.2&lt;/code&gt; and later (Workaround applied + upstream fix)&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/linuxserver/docker-airsonic"&gt;Airsonic&lt;/a&gt; (No log4j-core in use)&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/linuxserver/docker-habridge"&gt;HABridge&lt;/a&gt; (No log4j-core in use)&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/linuxserver/docker-unifi-controller"&gt;Unifi Controller&lt;/a&gt; - &lt;code&gt;version-6.5.55&lt;/code&gt; and later (Workaround applied + upstream fix)&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/linuxserver/docker-davos"&gt;Davos&lt;/a&gt; &lt;code&gt;version-2.2.2&lt;/code&gt; and later (Upstream fix)&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/linuxserver/docker-booksonic-air/"&gt;Booksonic Air&lt;/a&gt; - &lt;code&gt;version-v2112.2.0&lt;/code&gt; and later (Upstream fix)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;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&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://github.com/linuxserver/docker-unifi-controller"&gt;Unifi Controller&lt;/a&gt; - &lt;code&gt;version-6.5.54&lt;/code&gt; and later (Workaround applied + upstream fix)&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/linuxserver/docker-booksonic-air/"&gt;Booksonic Air&lt;/a&gt; - &lt;code&gt;version-v2112.1.0&lt;/code&gt; and later (Upstream fix)&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/linuxserver/docker-nzbhydra2"&gt;nzbhydra2&lt;/a&gt; - &lt;code&gt;version-v3.18.4&lt;/code&gt; and later (Upstream fix)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;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&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://github.com/linuxserver/docker-booksonic"&gt;Booksonic&lt;/a&gt; (Deprecated)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;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&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://github.com/linuxserver/docker-ubooquity"&gt;Ubooquity&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;We will update this post as more information becomes available.&lt;/p&gt;</content></item><item><title>New Container: Nzbhydra2</title><link>https://info.linuxserver.io/issues/2018-01-11-nzbhydra2/</link><pubDate>Thu, 11 Jan 2018 00:00:00 +0000</pubDate><guid>https://info.linuxserver.io/issues/2018-01-11-nzbhydra2/</guid><category/><description>&lt;p&gt;We have released a new container for &lt;a href="https://github.com/linuxserver/docker-nzbhydra2"&gt;Nzbhydra2&lt;/a&gt;!&lt;/p&gt;
&lt;p&gt;&lt;a href="https://github.com/theotherp/nzbhydra2"&gt;Nzbhydra2&lt;/a&gt; is a meta search application for NZB indexers, the &amp;ldquo;spiritual successor&amp;rdquo; to NZBmegasearcH, and an evolution of the original application &lt;a href="https://github.com/theotherp/nzbhydra"&gt;NZBHydra&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;It provides easy access to a number of raw and newznab based indexers. The application NZBHydra 2 is replacing NZBHydra 1 and supports migrating from V1. Be wary that there may be some compatibility issues for those migrating from V1 to V2, so ensure you back up your old configuration before moving over to the new version. &lt;strong&gt;NOTE:&lt;/strong&gt; The last version that supports migration is &lt;code&gt;linuxserver/nzbhydra2:v2.10.2-ls49&lt;/code&gt;&lt;/p&gt;</description><content type="html">&lt;p&gt;We have released a new container for &lt;a href="https://github.com/linuxserver/docker-nzbhydra2"&gt;Nzbhydra2&lt;/a&gt;!&lt;/p&gt;
&lt;p&gt;&lt;a href="https://github.com/theotherp/nzbhydra2"&gt;Nzbhydra2&lt;/a&gt; is a meta search application for NZB indexers, the &amp;ldquo;spiritual successor&amp;rdquo; to NZBmegasearcH, and an evolution of the original application &lt;a href="https://github.com/theotherp/nzbhydra"&gt;NZBHydra&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;It provides easy access to a number of raw and newznab based indexers. The application NZBHydra 2 is replacing NZBHydra 1 and supports migrating from V1. Be wary that there may be some compatibility issues for those migrating from V1 to V2, so ensure you back up your old configuration before moving over to the new version. &lt;strong&gt;NOTE:&lt;/strong&gt; The last version that supports migration is &lt;code&gt;linuxserver/nzbhydra2:v2.10.2-ls49&lt;/code&gt;&lt;/p&gt;</content></item></channel></rss>