CVE-2019-5097

No vendor fix yet; a mitigation is available.

• Mitigation1732E-8CFGM8R/Acisa_csaf_ot

  1756-EN2F/C: Update to 11.002 or later

• Mitigation1732E-8IOLM12Rcisa_csaf_ot

  1756-EN2F/C: Update to 11.002 or later

• Mitigation1732E-IB8M8SOERcisa_csaf_ot

  1756-EN2F/C: Update to 11.002 or later

• Mitigation1732E-IF4M12R/A (discontinued)cisa_csaf_ot

  1756-EN2F/C: Update to 11.002 or later

• Mitigation1732E-IR4IM12R/Acisa_csaf_ot

  1756-EN2F/C: Update to 11.002 or later

• Mitigation1732E-IT4IM12R/Acisa_csaf_ot

  1756-EN2F/C: Update to 11.002 or later

• Mitigation1732E-OB8M8SR/Acisa_csaf_ot

  1756-EN2F/C: Update to 11.002 or later

• Mitigation1732E-OF4M12R/Acisa_csaf_ot

  1756-EN2F/C: Update to 11.002 or later

• Mitigation1747-AENTRcisa_csaf_ot

  1756-EN2F/C: Update to 11.002 or later

• Mitigation1756- EN2T/Dcisa_csaf_ot

  1756-EN2F/C: Update to 11.002 or later

• Mitigation1756-EN2F/Ccisa_csaf_ot

  1756-EN2F/C: Update to 11.002 or later

• Mitigation1756-EN2T/Dcisa_csaf_ot

  1756-EN2F/C: Update to 11.002 or later

• Mitigation1756-EN2TP/Acisa_csaf_ot

  1756-EN2F/C: Update to 11.002 or later

• Mitigation1756-EN2TR/Ccisa_csaf_ot

  1756-EN2F/C: Update to 11.002 or later

• Mitigation1756-EN2TSC/Bcisa_csaf_ot

  1756-EN2F/C: Update to 11.002 or later

• Mitigation1756-EN2TSC/B (discontinued)cisa_csaf_ot

  1756-EN2F/C: Update to 11.002 or later

• Mitigation1756-HIST1G/A (discontinued)cisa_csaf_ot

  1756-EN2F/C: Update to 11.002 or later

• Mitigation1756-HIST2G/A(discontinued)cisa_csaf_ot

  1756-EN2F/C: Update to 11.002 or later

• Mitigation1756-HIST2G/Bcisa_csaf_ot

  1756-EN2F/C: Update to 11.002 or later

• Mitigation1765 - EN3TR/Bcisa_csaf_ot

  1756-EN2F/C: Update to 11.002 or later

• Mitigation1769-AENTRcisa_csaf_ot

  1756-EN2F/C: Update to 11.002 or later

• Mitigation5069-AEN2TRcisa_csaf_ot

  1756-EN2F/C: Update to 11.002 or later

• MitigationCompact GuardLogix 5380 controllerscisa_csaf_ot

  1756-EN2F/C: Update to 11.002 or later

• MitigationCompactLogix 5380 controllerscisa_csaf_ot

  1756-EN2F/C: Update to 11.002 or later

• MitigationCompactLogix 5480 controllerscisa_csaf_ot

  1756-EN2F/C: Update to 11.002 or later

• MitigationControlLogix 5580 controllerscisa_csaf_ot

  1756-EN2F/C: Update to 11.002 or later

• MitigationGuardLogix 5580 controllerscisa_csaf_ot

  1756-EN2F/C: Update to 11.002 or later

• MitigationMSMcisa_csaf_ot

  Hitachi Energy recommends following general mitigation factors. MSM is not intrinsically designed to be directly connected to the internet. Disconnect the device from any internet-facing network, if any installation has performed the same. It is recommended to adopt user access management controls and state-of-the-art antivirus software equipped with the latest signature rules on computers that have the MSM Client application installed and running. As an example, please use the operating system's (OS) built-in user access management functionality, if supported, to limit the probability of unauthorized access followed by rogue commands via MSM Client application. It is also recommended to follow the hardening guidelines published by the Center for Internet Security (CIS) https://www.cisecurity.org/about-us/ to protect the host operating system of computers that connect with MSM. This measure would then prevent the lateral movement of the attack vector into MSM via these connected devices. Some examples for Windows-based computers are listed here. 1) CIS Microsoft Windows Desktop Benchmarks (cisecurity.org) 2) CIS Microsoft Windows Server Benchmarks (cisecurity.org) Cybersecurity Advisory - Industrial Control Systems Cybersecurity Best Practices https://publisher.hitachienergy.com/preview?DocumentID=8DBD000235&LanguageCode=en&DocumentPartId=&Action=Launch