AVEVA Fixes Vijeo Citect, Citect SCADA Hole

Tuesday, November 27, 2018 @ 07:11 PM gHale

AVEVA Software, LLC (AVEVA) has upgraded software to mitigate an uncontrolled search path element in its Vijeo Citect and Citect SCADA, according to a report from NCCIC.

Successful exploitation of this vulnerability, which AVEVA self-reported, could allow an attacker to execute arbitrary code on the target system.

RELATED STORIES
Schneider Mitigations for Modicon M221 Hole
Teledyne DALSA Updates Sherlock Issue
Siemens Fixes SIMATIC Panels
SIMATIC IT Production Suite Hole Fixed

AVEVA reports that a vulnerability in Schneider Electric Software Update utility versions prior to v2.2.0 affects the following AVEVA products:
• Vijeo Citect v7.40
• Vijeo Citect 2015
• Citect SCADA v7.40
• Citect SCADA 2015
• Citect SCADA 2016

The product uses a fixed or controlled search path to find resources. An attacker with local access could place a specially crafted file on the target machine, which may give the attacker the ability to execute arbitrary code.

CVE-2018-7799 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 7.8.

The product sees use mainly in the commercial facilities, critical manufacturing and energy sectors. It also sees action on a global basis.

AVEVA reported this vulnerability to NCCIC.

No known public exploits specifically target this vulnerability. This vulnerability is not exploitable remotely.

AVEVA recommends all affected users download and upgrade to the latest version of the Schneider Electric Software Update (SESU) software.

Click here to view AVEVA’s Security Advisory.

AVEVA recommends following industry cybersecurity best practices, such as:
• Locate control and safety system networks and remote devices behind firewalls, and isolate them from the business network.
• Physical controls should be in place so that no unauthorized person would have access to the ICS and safety controllers, peripheral equipment or the ICS and safety networks.
• All controllers should reside in locked cabinets and never be left in the “Program” mode.
• All programming software should be kept in locked cabinets and should never be connected to any network other than the network for the devices that it is intended.
• All methods of mobile data exchange with the isolated network such as CDs, USB drives, etc. should be scanned before use in the terminals or any node connected to these networks.
• Laptops that have connected to any other network besides the intended network should never be allowed to connect to the safety or control networks without proper sanitation.
• Minimize network exposure for all control system devices and/or systems, and ensure that they are not accessible from the Internet.
• When remote access is required, use secure methods, such as Virtual Private Networks (VPNs), recognizing that VPNs may have vulnerabilities and should be updated to the most current version available. Also recognize that VPN is only as secure as the connected devices.



Leave a Reply

You must be logged in to post a comment.