Search Results for: log4j
Is VMware going to update log4j to version 2.17
As we know by now that the only solution for Log4j is to get it updated to version 2.17. The question is if VMware is…
VMware is going to update log4j to version 2.16
Today VMware published update on log4j solution. As per statment on the vendor KB website says that VMware expect to fully address both CVE-2021-44228 and…
-Dlog4j2.formatMsgNoLookups=true” or “class JndiLookup” is not valid workaround anymore!
It looks like to workaround published by VMware is not valid anymore! On December 9, 2021 VMware released VMSA-2021-0028 to track the impact of an…
Patching time! VMware released an update for vCenter Server and ESXi -> 7.0 Update 3f.
vCenter server: NOTE: If your source system contains hosts of versions between ESXi 7.0 Update 2 and Update 3c, and Intel drivers, before upgrading to…
Angry Admin blog made it! I received vExpert 2022 award!
The first time I heard about vExpert program it was around June 2021. My blog was only 3 months old and I knew it was…
Angry Admin was a guest on VMware CMTY Podcast #593
Few days back I received an email form VMware inviting me for a podcast. The reason for invitation was one of my posts about log4j…
vCenter Server 7.0 Update 3c has been released.
Finally, VMware released a new update for vCenter Server addressing all the issues documented in KB86281, also including Apache log4j version 2.17. IMPORTANT: VMware removed ESXi…
Update on VMSA-2021-0028
NSX-T Data Center (2.5.0-3.1.3) (KB87086) – https://kb.vmware.com/s/article/87086?lang=en_US •December 17th 2021 – 15:00 PST [6:00PM EST]: Added detail regarding NSX T 3.2.0 release pertinent to CVE-2021-44228 & CVE-2021-45046….
VMware Site Recovery Manager is getting patch to resolve CVE-2021-44228 and CVE-2021-45046.
VMware just published a patch for SRM 8.5.0.2 where Apache log4j is updated to version 2.16 to resolve CVE-2021-44228 and CVE-2021-45046. If you are running…
Additional step for vCenter Server CVE-2021-44228 and CVE-2021-45046 workaround.
VMware just updated their KB adding additional step which needs to be run even if someone already did apply workaround. This additional step is to…