<?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 log4j: Horizon Update ?'s in Horizon Desktops and Apps</title>
    <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/log4j-Horizon-Update-s/m-p/2888550#M96014</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;We updated our Horizon to 7.13.1 to remediate the log4j vulnerabilities. However, scans are still flagging our agents in the following directory: Program Files/VMware/VMware View/Agent/lib/v4pa. The three log4j files in that directory are, log4j-1.2.16, log4j-api-2.16.0 and log4j-core-2.16.0. Is there a reason why the log4j-1.2.16 was not upgraded to 2.16.0 to?&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 17 Jan 2022 20:32:51 GMT</pubDate>
    <dc:creator>onlyroad</dc:creator>
    <dc:date>2022-01-17T20:32:51Z</dc:date>
    <item>
      <title>log4j: Horizon Update ?'s</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/log4j-Horizon-Update-s/m-p/2888550#M96014</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;We updated our Horizon to 7.13.1 to remediate the log4j vulnerabilities. However, scans are still flagging our agents in the following directory: Program Files/VMware/VMware View/Agent/lib/v4pa. The three log4j files in that directory are, log4j-1.2.16, log4j-api-2.16.0 and log4j-core-2.16.0. Is there a reason why the log4j-1.2.16 was not upgraded to 2.16.0 to?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 17 Jan 2022 20:32:51 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/log4j-Horizon-Update-s/m-p/2888550#M96014</guid>
      <dc:creator>onlyroad</dc:creator>
      <dc:date>2022-01-17T20:32:51Z</dc:date>
    </item>
  </channel>
</rss>

