Hello all,
our company securitry scans found that the HTTP Track and Trace Methods on vcenter are accepted, which means that this is a vulnerability.
Recommdened Fix is to turn off TraceEnable in httpd.conf
Please note that RewriteEngine can be processor intensive and may impact the web server performance. The trace method can also be controlled by use of the TraceEnable directive.
In the httpd.conf add or modify:
TraceEnable Off
Its for this ports:
40920/tcp
44134/tcp
50506/tcp
36672/tcp
I have no idea which service used this ports.
Where can i config TraceEnable off on vcenter - global for every service not just for http and https, also for lifecycle manager, etc..
Thx,
Michhael
Comment removed...
Hello,
this is the workaround:
Backup all war files!!
Run the command mkdir /tmp/war/
Run the command cp /usr/lib/vmware-updatemgr/bin/jetty/webapps/root.war /tmp/war/
Run the command cd /tmp/war/
Unzip the root.war file.
Run the command cd WEB-INF/
Run the command chmod 777 web.xml
Edit web.xml and add the following code after the last <servlet-mapping> tag:
<security constraint>
<web resource collection>
<web-resource-name>Restricted HTTP Methods</web-resource-name>
<url-pattern>/*</url-pattern>
<http method>TRACE</http method>
</web-resource-collection>
<auth constraint />
</security-constraint>
cd ..
Run the command zip -r -u root.war WEB-INF/
Run the command cp root.war /usr/lib/vmware-updatemgr/bin/jetty/webapps/
Clean /tmp/war with rm -rf /tmp/war/*
Repeat steps 2 to 11 for vum-filedownload.war and vum-fileupload.war
Restart the updatemgr service.
Comment removed...
Hi,
I found this vulnerability in version 7, but not in version 8. For version 7 , go through the below release note document:
For version 8, it better to open a ticket with vmware.
Regards,
Sachchidanand
Comment removed...