VMWare vCenter Log4J Workaround | VMSA-2021-0028 | CVE-2021-44228

preview_player
Показать описание
Apply the workaround for Log4J to your VMWare vCenter appliance. This covers vulnerability VMSA-2021-0028, CVE-2021-44228. You will need PuTTY and WinSCP for this.

####################################################################
FOLLOW ME:
---------------------------------------------------

VIDEO EQUIPMENT (Affiliate Links):
---------------------------------------------------

BUSINESS INQUIERIES:
---------------------------------------------------
Рекомендации по теме
Комментарии
Автор

When you SSH into the vcenter appliance, you might not see the shell option. You will need to enable it, go to your vcenter on port 5480 and under Access enable Bash shell for 60 minutes. Then SSH again and you should get the option. Thanks for making videos like this. Really a great help for the community, and good luck growing the channel.

larsstampe
Автор

Thank you this video. This was big help in patching one of my servers. subbed!!

linux_engineer
Автор





WinSCP SFTP Settings: shell /usr/libexec/sftp-server (Uncheck allow SFTP Fallback)
PuTTY: shell.set --enabled True

thecybersecuritymindset
Автор

Will running the script restart all my virtual machines?

jstinn
Автор

You said to take snapshot of vm, but we are in cli mode. How can i achieve that? Sorry i am new for Vsphere client

PularKhan-ldyd
Автор

Does this affect running VMs or is it possible to do the script while machines are up?
Thanks in advance!

gilethir
Автор

does this log4j Vul effects all VMWare vCenter appliance versions or some specific versions only ?

umairiqbal