Thanks, Brian.
As an FYI, I Opened a case with Symantec and below is the recommendation:
Customers using an affected version should block general access to port 8445 on their SEPM to mitigate this vulnerability until a product update is available.
To temporarily mitigate the vulnerability before you upgrade the Symantec Endpoint Protection Manager console, you can block the affected port with a firewall rule. However, if you block the port, the management console loses specific functionality. You should review the implications prior to implementation.
Note: The port mentioned below is the Symantec Endpoint Protection Manager default reporting port. If you have changed the reporting port, please alter the firewall rules appropriately.
Steps: Add a firewall rule to block the specific port on the computer on which you installed Symantec Endpoint Protection Manager. This firewall rule should apply to all hosts and all applications.
To confirm that the rule applied successfully, simply telnet to the port. If the rule is configured correctly, the firewall successfully blocks traffic and does not permit a connection on the port.
Note: For instructions on creating a firewall rule using the Symantec Endpoint Protection client, please see HOWTO81156: Adding a new firewall rule. If you configure the policy from the Symantec Endpoint Protection Manager, you will need to wait for the policy to propagate to the Symantec Endpoint Protection client installed on the SEPM server prior to testing. To force the SEP client to download the modified policy immediately, right-click the SEP system-tray icon and click Update Policy.
Implications: If an administrator logs in to the SEPM with port 8445 blocked, the first three reporting tabs (Home, Monitors, and Reports) will not display in the Remote Java console. Blocking port 8445 will deny access to the Remote Reporting Console as well. Administrators may configure firewall rules to allow access to port 8445 or 443 from explicit hosts, IP addresses, or IP address ranges to enable these features.
Secure client/server communications: If FIPS mode is enabled, or if SEP has been configured to use secure client/server communication, port 443 is used for client/server communications. In these cases, port 443 should be restricted. Blocking port 443 denies communication to and from all clients that are using secure communication. Administrators can configure firewall rules to allow access to port 443 from explicit hosts, IP addresses, or IP address ranges to enable these features