<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Apache CVE-2021-44228 log4j Remote Code Execution Vulnerability Resolution]]></title><description><![CDATA[<p dir="auto">On December 9th, 2021, an exploit was discovered in the widely used Apache Log4j logging libraries.  This bug exposes a class of security vulnerability known as a Remote Code Execution Vulnerability.  This package is widely used in Java-based enterprise applications and cloud services across verticals and institutions worldwide. Mango also uses this package.</p>
<p dir="auto">Following the publication of this information by Apache, Radix has produced two high-priority security updates:<br />
•	4.2.4 which is an update to the 4.2 series of Mango.<br />
•	3.7.9 is an update to the legacy 3.7 series of Mango.</p>
<p dir="auto">All customers, specifically those with public IP-facing connections, should immediately upgrade to mitigate the risk of this exploit.</p>
<p dir="auto">For customers that are unable for technical reasons to upgrade to these newest versions, the is a manual alternative that can be followed below depending on your version.</p>
<p dir="auto">Further public information can be found on this exploit here: <a href="https://www.cisa.gov/uscert/ncas/current-activity/2021/12/10/apache-releases-log4j-version-2150-address-critical-rce" rel="nofollow ugc">https://www.cisa.gov/uscert/ncas/current-activity/2021/12/10/apache-releases-log4j-version-2150-address-critical-rce</a></p>
<p dir="auto"><strong>Version: Mango 4.0+</strong></p>
<p dir="auto"><em>Linux Environments</em></p>
<p dir="auto">If you are starting Mango via <a href="http://start-mango.sh" rel="nofollow ugc">start-mango.sh</a> or our supplied systemd mango.service file:</p>
<ul>
<li>If you do not have <a href="http://start-options.sh" rel="nofollow ugc">start-options.sh</a> in your data directory:
<ul>
<li>Copy <a href="http://start-options.sh" rel="nofollow ugc">start-options.sh</a> from Mango installation directory to your data directory</li>
<li>Edit <a href="http://start-options.sh" rel="nofollow ugc">start-options.sh</a> and add the following line:</li>
</ul>
</li>
</ul>
<pre><code>MA_JAVA_OPTS="$MA_JAVA_OPTS -Dlog4j2.formatMsgNoLookups=true"
</code></pre>
<ul>
<li>Restart Mango</li>
</ul>
<p dir="auto">Verify that Mango loaded your <a href="http://start-options.sh" rel="nofollow ugc">start-options.sh</a> file and the java process was started with the -Dlog4j2.formatMsgNoLookups=true option:</p>
<pre><code>ps aux | grep java
</code></pre>
<p dir="auto">If you are not using Mango's supplied <a href="http://start-mango.sh" rel="nofollow ugc">start-mango.sh</a> or mango.service file to start Mango:</p>
<ul>
<li>Set the Java system property log4j2.formatMsgNoLookups=true (This is done by providing the following argument to java -Dlog4j2.formatMsgNoLookups=true)</li>
<li>Restart Mango</li>
</ul>
<p dir="auto"><em>Windows Environments</em></p>
<ul>
<li>Ensure the java property log4j2.formatMsgNoLookups is set to true.  This is done by adding -Dlog4j2.formatMsgNoLookups=true to the Java command that starts Mango.</li>
<li>Restart Mango</li>
</ul>
<p dir="auto"><strong>Version: Mango 3.6-3.7</strong></p>
<p dir="auto"><em>Linux Environments</em><br />
The fix is dependent on how Mango is being started.  By default Mango will use the <a href="http://ma.sh" rel="nofollow ugc">ma.sh</a> start command, if you are using this command:</p>
<ul>
<li>Add an extension to the bin/ext-enabled folder that is an executable file with this content:</li>
</ul>
<pre><code>#!/bin/bash

case "$1" in

    init)

    #Disable lookups during message formatting

  JAVAOPTS="$JAVAOPTS -Dlog4j2.formatMsgNoLookups=true"

        ;;

esac
</code></pre>
<ul>
<li>Restart Mango</li>
</ul>
<p dir="auto"><em>Windows Environments</em></p>
<ul>
<li>Ensure the java property log4j2.formatMsgNoLookups is set to true.  This is done by adding -Dlog4j2.formatMsgNoLookups=true to the Java command that starts Mango.</li>
<li>Restart Mango</li>
</ul>
<p dir="auto">If you have questions please contact Radix IOT customer support at <a href="mailto:support@radixiot.com" rel="nofollow ugc">support@radixiot.com</a></p>
]]></description><link>https://forum.mango-os.com/topic/5404/apache-cve-2021-44228-log4j-remote-code-execution-vulnerability-resolution</link><generator>RSS for Node</generator><lastBuildDate>Thu, 14 May 2026 01:38:48 GMT</lastBuildDate><atom:link href="https://forum.mango-os.com/topic/5404.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 10 Dec 2021 21:12:58 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Apache CVE-2021-44228 log4j Remote Code Execution Vulnerability Resolution on Mon, 20 Dec 2021 16:47:32 GMT]]></title><description><![CDATA[<p dir="auto">Update: There is a 3rd vulnerability reported in log4j - <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45105" rel="nofollow ugc">CVE-2021-45105</a></p>
<p dir="auto">Mango is not affected by this particular vulnerability as</p>
<ul>
<li>Mango does not use a context lookup in any of the patterns in the <a href="https://github.com/MangoAutomation/ma-core-public/blob/4.2.x/Core/resources/log4j2.xml" rel="nofollow ugc">supplied log4j2.xml file</a></li>
<li>Our codebase does not make use of the <code>org.apache.logging.log4j.ThreadContext</code> class</li>
</ul>
<p dir="auto">For more information, please see <a href="https://logging.apache.org/log4j/2.x/security.html" rel="nofollow ugc">https://logging.apache.org/log4j/2.x/security.html</a></p>
<p dir="auto">Mango will update to Log4J version 2.17.0 with our next release, however we do not believe this new CVE warrants an immediate patch.</p>
]]></description><link>https://forum.mango-os.com/post/27200</link><guid isPermaLink="true">https://forum.mango-os.com/post/27200</guid><dc:creator><![CDATA[Jared Wiltshire]]></dc:creator><pubDate>Mon, 20 Dec 2021 16:47:32 GMT</pubDate></item><item><title><![CDATA[Reply to Apache CVE-2021-44228 log4j Remote Code Execution Vulnerability Resolution on Tue, 14 Dec 2021 22:36:51 GMT]]></title><description><![CDATA[<p dir="auto"><a href="https://store.mango-os.com/core/3.7.11" rel="nofollow ugc">Mango 3.7.11</a> has been released</p>
<blockquote>
<p dir="auto">Update log4j2 to version 2.16.0, fix for CVE-2021-45046</p>
</blockquote>
]]></description><link>https://forum.mango-os.com/post/27183</link><guid isPermaLink="true">https://forum.mango-os.com/post/27183</guid><dc:creator><![CDATA[Jared Wiltshire]]></dc:creator><pubDate>Tue, 14 Dec 2021 22:36:51 GMT</pubDate></item><item><title><![CDATA[Reply to Apache CVE-2021-44228 log4j Remote Code Execution Vulnerability Resolution on Tue, 14 Dec 2021 21:57:02 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/jared-wiltshire" aria-label="Profile: jared-wiltshire">@<bdi>jared-wiltshire</bdi></a> Awesome! Thanks for the super speedy update.</p>
]]></description><link>https://forum.mango-os.com/post/27181</link><guid isPermaLink="true">https://forum.mango-os.com/post/27181</guid><dc:creator><![CDATA[dhckris]]></dc:creator><pubDate>Tue, 14 Dec 2021 21:57:02 GMT</pubDate></item><item><title><![CDATA[Reply to Apache CVE-2021-44228 log4j Remote Code Execution Vulnerability Resolution on Tue, 14 Dec 2021 21:40:48 GMT]]></title><description><![CDATA[<p dir="auto"><a href="https://store.mango-os.com/core/4.2.5" rel="nofollow ugc">Mango 4.2.5</a> has been released</p>
<blockquote>
<p dir="auto">Update log4j2 to version 2.16.0, fix for CVE-2021-45046</p>
</blockquote>
]]></description><link>https://forum.mango-os.com/post/27180</link><guid isPermaLink="true">https://forum.mango-os.com/post/27180</guid><dc:creator><![CDATA[Jared Wiltshire]]></dc:creator><pubDate>Tue, 14 Dec 2021 21:40:48 GMT</pubDate></item><item><title><![CDATA[Reply to Apache CVE-2021-44228 log4j Remote Code Execution Vulnerability Resolution on Tue, 14 Dec 2021 21:19:43 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/dhckris" aria-label="Profile: dhckris">@<bdi>dhckris</bdi></a> said in <a href="/post/27178">Apache CVE-2021-44228 log4j Remote Code Execution Vulnerability Resolution</a>:</p>
<blockquote>
<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/mumcs01" aria-label="Profile: mumcs01">@<bdi>mumcs01</bdi></a> Thank you for the post!<br />
Any timeline on updating to log4j 2.16?<br />
Apache put out a bulletin [1] regarding there still being pathways to exploit  that 2.15 doesn't resolve.<br />
[1] <a href="https://logging.apache.org/log4j/2.x/security.html" rel="nofollow ugc">https://logging.apache.org/log4j/2.x/security.html</a></p>
</blockquote>
<p dir="auto">Mango by default would not be affected by <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45046" rel="nofollow ugc">CVE-2021-45046</a> as we do not use the patterns mentioned in our default logging configuration. However since users have the ability to customize their Log4J configurations we will schedule another release to upgrade to Log4J 2.16.0. Better safe than sorry!</p>
]]></description><link>https://forum.mango-os.com/post/27179</link><guid isPermaLink="true">https://forum.mango-os.com/post/27179</guid><dc:creator><![CDATA[Jared Wiltshire]]></dc:creator><pubDate>Tue, 14 Dec 2021 21:19:43 GMT</pubDate></item><item><title><![CDATA[Reply to Apache CVE-2021-44228 log4j Remote Code Execution Vulnerability Resolution on Tue, 14 Dec 2021 20:30:29 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/mumcs01" aria-label="Profile: mumcs01">@<bdi>mumcs01</bdi></a> Thank you for the post!<br />
Any timeline on updating to log4j 2.16?<br />
Apache put out a bulletin [1] regarding there still being pathways to exploit  that 2.15 doesn't resolve.<br />
[1] <a href="https://logging.apache.org/log4j/2.x/security.html" rel="nofollow ugc">https://logging.apache.org/log4j/2.x/security.html</a></p>
]]></description><link>https://forum.mango-os.com/post/27178</link><guid isPermaLink="true">https://forum.mango-os.com/post/27178</guid><dc:creator><![CDATA[dhckris]]></dc:creator><pubDate>Tue, 14 Dec 2021 20:30:29 GMT</pubDate></item><item><title><![CDATA[Reply to Apache CVE-2021-44228 log4j Remote Code Execution Vulnerability Resolution on Sat, 11 Dec 2021 22:38:43 GMT]]></title><description><![CDATA[<p dir="auto">Additionally, the following test can be performed at a command prompt to test if the instance of Mango is vulnerable:</p>
<p dir="auto">Execute the following:</p>
<pre><code>curl "https://mango.example.com:8443/$\{java:runtime\}" --data ""
</code></pre>
<p dir="auto">Following this, Check the ma.log file or stdout</p>
<p dir="auto">If the instance is vulnerable you will see the following:</p>
<pre><code>WARN  2021-12-10T15:50:05,553 (com.serotonin.m2m2.web.mvc.spring.security.MangoAccessDeniedHandler.handle:65)[MangoAccessDeniedHandler] - Access denied to resource '/OpenJDK Runtime Environment (build 17+35-LTS) from Azul Systems, Inc.', for user '', IP address '127.0.0.1'
</code></pre>
<p dir="auto">If the instance is already patched and not vulnerable you will be the following:</p>
<pre><code>WARN  2021-12-10T15:53:31,895 (com.serotonin.m2m2.web.mvc.spring.security.MangoAccessDeniedHandler.handle:65)[MangoAccessDeniedHandler] - Access denied to resource '/${java:runtime}', for user '', IP address '127.0.0.1'
</code></pre>
]]></description><link>https://forum.mango-os.com/post/27175</link><guid isPermaLink="true">https://forum.mango-os.com/post/27175</guid><dc:creator><![CDATA[mumcs01]]></dc:creator><pubDate>Sat, 11 Dec 2021 22:38:43 GMT</pubDate></item></channel></rss>