<?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: Critical OpenSSL Vulnerability in Management &amp; Governance</title>
    <link>https://community.qlik.com/t5/Management-Governance/Critical-OpenSSL-Vulnerability/m-p/2513313#M31806</link>
    <description>&lt;P&gt;Fair enough.. lets cross our fingers i guess..&lt;/P&gt;</description>
    <pubDate>Mon, 07 Apr 2025 08:40:37 GMT</pubDate>
    <dc:creator>tin_u</dc:creator>
    <dc:date>2025-04-07T08:40:37Z</dc:date>
    <item>
      <title>Critical OpenSSL Vulnerability</title>
      <link>https://community.qlik.com/t5/Management-Governance/Critical-OpenSSL-Vulnerability/m-p/2505866#M29107</link>
      <description>&lt;P&gt;Good day&lt;BR /&gt;&lt;BR /&gt;When should we expect the release of&amp;nbsp;&lt;SPAN&gt;QB-28631 or QB-28762, now we are sitting with a situation (&lt;A href="https://cyberpress.org/openssl-vulnerability/" target="_blank"&gt;https://cyberpress.org/openssl-vulnerability/&lt;/A&gt;) and Microsoft Defender has picked up Qlik Sense's OpenSSL files need to be updated.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Affected Files:&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;c:\program files\common files\qlik\custom data\qvodbcconnectorpackage\drill\lib\openssl64.dlla\libcrypto-3-x64.dll&lt;BR /&gt;c:\program files\common files\qlik\custom data\qvodbcconnectorpackage\drill\lib\openssl64.dlla\libssl-3-x64.dll&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;c:\programdata\package cache\af7aeebf-6f94-4a09-9113-21295ed47105\qvodbcconnectorpackage\oracle\lib\libcrypto-3-x64.dll&lt;BR /&gt;c:\programdata\package cache\af7aeebf-6f94-4a09-9113-21295ed47105\qvodbcconnectorpackage\oracle\lib\libssl-3-x64.dll&lt;BR /&gt;c:\programdata\package cache\af7aeebf-6f94-4a09-9113-21295ed47105\qvodbcconnectorpackage\spark\lib\libcurl64.dlla\openssl64.dlla\libcrypto-3-x64.dll&lt;/P&gt;
&lt;P&gt;c:\programdata\package cache\af7aeebf-6f94-4a09-9113-21295ed47105\qvodbcconnectorpackage\spark\lib\libcurl64.dlla\openssl64.dlla\libssl-3-x64.dll&lt;BR /&gt;c:\programdata\package cache\af7aeebf-6f94-4a09-9113-21295ed47105\qvodbcconnectorpackage\spark\lib\openssl64.dlla\libcrypto-3-x64.dll&lt;BR /&gt;c:\programdata\package cache\af7aeebf-6f94-4a09-9113-21295ed47105\qvodbcconnectorpackage\spark\lib\openssl64.dlla\libssl-3-x64.dll&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;cc:&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/160205"&gt;@Lass&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 14 Feb 2025 05:36:38 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Critical-OpenSSL-Vulnerability/m-p/2505866#M29107</guid>
      <dc:creator>BernieMaf</dc:creator>
      <dc:date>2025-02-14T05:36:38Z</dc:date>
    </item>
    <item>
      <title>Re: Critical OpenSSL Vulnerability</title>
      <link>https://community.qlik.com/t5/Management-Governance/Critical-OpenSSL-Vulnerability/m-p/2506540#M29108</link>
      <description>&lt;P&gt;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/130975"&gt;@Nick_Asilo&lt;/a&gt;&amp;nbsp;can you please assist?&lt;/P&gt;</description>
      <pubDate>Wed, 19 Feb 2025 08:27:42 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Critical-OpenSSL-Vulnerability/m-p/2506540#M29108</guid>
      <dc:creator>BernieMaf</dc:creator>
      <dc:date>2025-02-19T08:27:42Z</dc:date>
    </item>
    <item>
      <title>Re: Critical OpenSSL Vulnerability</title>
      <link>https://community.qlik.com/t5/Management-Governance/Critical-OpenSSL-Vulnerability/m-p/2512742#M31793</link>
      <description>&lt;P&gt;Do we have any status on this that Qlik recognize this as an issue?&lt;/P&gt;</description>
      <pubDate>Wed, 02 Apr 2025 12:25:42 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Critical-OpenSSL-Vulnerability/m-p/2512742#M31793</guid>
      <dc:creator>tin_u</dc:creator>
      <dc:date>2025-04-02T12:25:42Z</dc:date>
    </item>
    <item>
      <title>Re: Critical OpenSSL Vulnerability</title>
      <link>https://community.qlik.com/t5/Management-Governance/Critical-OpenSSL-Vulnerability/m-p/2512746#M31794</link>
      <description>&lt;P&gt;Nothing at all.&lt;BR /&gt;QLIK support is non-existent on issues we raise. I guess they are willing to pay when we get breached because of their products.&lt;BR /&gt;Security is not that important to them, postmen are quicker than their security team when it comes to delivery.&lt;/P&gt;</description>
      <pubDate>Wed, 02 Apr 2025 12:43:11 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Critical-OpenSSL-Vulnerability/m-p/2512746#M31794</guid>
      <dc:creator>BernieMaf</dc:creator>
      <dc:date>2025-04-02T12:43:11Z</dc:date>
    </item>
    <item>
      <title>Re: Critical OpenSSL Vulnerability</title>
      <link>https://community.qlik.com/t5/Management-Governance/Critical-OpenSSL-Vulnerability/m-p/2513004#M31796</link>
      <description>&lt;P&gt;Just got a reply from support regarding my ticket where i raised some of these concerns, and it seems like these issues will be addressed in the May 2025 Initial Release..&lt;/P&gt;</description>
      <pubDate>Thu, 03 Apr 2025 14:31:31 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Critical-OpenSSL-Vulnerability/m-p/2513004#M31796</guid>
      <dc:creator>tin_u</dc:creator>
      <dc:date>2025-04-03T14:31:31Z</dc:date>
    </item>
    <item>
      <title>Re: Critical OpenSSL Vulnerability</title>
      <link>https://community.qlik.com/t5/Management-Governance/Critical-OpenSSL-Vulnerability/m-p/2513009#M31797</link>
      <description>&lt;P&gt;I won't get my hopes up. We were told last year that it would be addressed in the November 2024 release, but here we are.&lt;/P&gt;</description>
      <pubDate>Thu, 03 Apr 2025 14:35:11 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Critical-OpenSSL-Vulnerability/m-p/2513009#M31797</guid>
      <dc:creator>BernieMaf</dc:creator>
      <dc:date>2025-04-03T14:35:11Z</dc:date>
    </item>
    <item>
      <title>Re: Critical OpenSSL Vulnerability</title>
      <link>https://community.qlik.com/t5/Management-Governance/Critical-OpenSSL-Vulnerability/m-p/2513313#M31806</link>
      <description>&lt;P&gt;Fair enough.. lets cross our fingers i guess..&lt;/P&gt;</description>
      <pubDate>Mon, 07 Apr 2025 08:40:37 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Critical-OpenSSL-Vulnerability/m-p/2513313#M31806</guid>
      <dc:creator>tin_u</dc:creator>
      <dc:date>2025-04-07T08:40:37Z</dc:date>
    </item>
    <item>
      <title>Re: Critical OpenSSL Vulnerability</title>
      <link>https://community.qlik.com/t5/Management-Governance/Critical-OpenSSL-Vulnerability/m-p/2513316#M31807</link>
      <description>&lt;P&gt;I have already gone through the Technical Preview for May 2025&amp;nbsp;&lt;A href="https://community.qlik.com/t5/Release-Notes/Qlik-Sense-Enterprise-on-Windows-Technical-Preview-for-May-2025/ta-p/2512973" target="_blank"&gt;https://community.qlik.com/t5/Release-Notes/Qlik-Sense-Enterprise-on-Windows-Technical-Preview-for-May-2025/ta-p/2512973&lt;/A&gt;&amp;nbsp;and I don't see the resolution for our issue.&lt;BR /&gt;The only thing close to our issue is the QB-29866 (&lt;SPAN&gt;Qlik Sense: libcurl library updates).&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 07 Apr 2025 08:53:45 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Critical-OpenSSL-Vulnerability/m-p/2513316#M31807</guid>
      <dc:creator>BernieMaf</dc:creator>
      <dc:date>2025-04-07T08:53:45Z</dc:date>
    </item>
  </channel>
</rss>

