Step 2 - vCenter ServerĪfter that, proceed with the rest of your VMware systems running Log4j: vCenter Server, WS1 Access / Identity Manager, Log Insight, etc. The workaround has to be implemented on all agents, including the master image(s) used for cloning. Workaround for Horizon Server: VMware KB #87073Īfter securing the internet-accessible servers, follow the instructions above and implement the patch/workaround for the remaining Horizon server(s) and then the Horizon agents. If you can't upgrade, implement the latest workarounds: Workaround for UAG: VMware KB #87092.
Upgrade to the following versions, if you can: Consider cutting them off from the internet, both for incoming and outgoing traffic, until the patch/workaround is fully implemented. Identify which UAG or Horizon components are reachable from the internet, and start with those. (Update, 15:30 CET: Added information about vCenter Server 7.0 patches being released) Step 1 - VMware Horizon/UAG (Update, 10:30 CET: Added information about Horizon patches being released, and the updated information about vCenter patching)
(Update, 17:00 CET: Added information about a workaround for vCenter Server) (Update, 21:00 CET: Workaround for UAG has just been announced, see link below)
0 kommentar(er)
