<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: about log4j issue in Management &amp; Governance</title>
    <link>https://community.qlik.com/t5/Management-Governance/about-log4j-issue/m-p/1893534#M30228</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/159942"&gt;@FWD_Qlik_Support&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;As per the article below,&amp;nbsp;as of&lt;STRONG&gt;&amp;nbsp;Feb. 15, 2022.&amp;nbsp;&lt;/STRONG&gt;All current threats have been addressed.&amp;nbsp;&lt;BR /&gt;&lt;A href="https://community.qlik.com/t5/Support-Updates-Blog/Vulnerability-Testing-Apache-Log4j-reference-CVE-2021-44228-also/ba-p/1869368/page/3#commentsc" target="_blank"&gt;https://community.qlik.com/t5/Support-Updates-Blog/Vulnerability-Testing-Apache-Log4j-reference-CVE-2021-44228-also/ba-p/1869368/page/3#comments&amp;nbsp;&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 16 Feb 2022 07:44:07 GMT</pubDate>
    <dc:creator>Seanog_Murphy</dc:creator>
    <dc:date>2022-02-16T07:44:07Z</dc:date>
    <item>
      <title>about log4j issue</title>
      <link>https://community.qlik.com/t5/Management-Governance/about-log4j-issue/m-p/1893199#M30227</link>
      <description>&lt;P&gt;We have temporarily modified the configuration file to fix the vulnerability of log4j. Is there an updated version for log4j now？&lt;/P&gt;</description>
      <pubDate>Wed, 29 Jan 2025 16:38:32 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/about-log4j-issue/m-p/1893199#M30227</guid>
      <dc:creator>FWD_Qlik_Support</dc:creator>
      <dc:date>2025-01-29T16:38:32Z</dc:date>
    </item>
    <item>
      <title>Re: about log4j issue</title>
      <link>https://community.qlik.com/t5/Management-Governance/about-log4j-issue/m-p/1893534#M30228</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/159942"&gt;@FWD_Qlik_Support&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;As per the article below,&amp;nbsp;as of&lt;STRONG&gt;&amp;nbsp;Feb. 15, 2022.&amp;nbsp;&lt;/STRONG&gt;All current threats have been addressed.&amp;nbsp;&lt;BR /&gt;&lt;A href="https://community.qlik.com/t5/Support-Updates-Blog/Vulnerability-Testing-Apache-Log4j-reference-CVE-2021-44228-also/ba-p/1869368/page/3#commentsc" target="_blank"&gt;https://community.qlik.com/t5/Support-Updates-Blog/Vulnerability-Testing-Apache-Log4j-reference-CVE-2021-44228-also/ba-p/1869368/page/3#comments&amp;nbsp;&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 16 Feb 2022 07:44:07 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/about-log4j-issue/m-p/1893534#M30228</guid>
      <dc:creator>Seanog_Murphy</dc:creator>
      <dc:date>2022-02-16T07:44:07Z</dc:date>
    </item>
  </channel>
</rss>

