ICSA-17-201-01

icsaUScisa_csaf_ot

Schneider Electric PowerSCADA Anywhere and Citect Anywhere

view advisory published 2017-07-20

ATTENTION: Remotely exploitable/low skill level to exploit.

01

describes (4)

Related CVEs.

IDseverity exploitable
CVE-2017-7972USmedium5.5—
A vulnerability exists in Schneider Electric's PowerSCADA Anywhere v1.0 redistributed with PowerSCADA Expert v8.1 and PowerSCADA Expert v8.2 and Citect Anywhere version 1.0 that al…
CVE-2017-7971USmedium6.5—
A vulnerability exists in Schneider Electric's PowerSCADA Anywhere v1.0 redistributed with PowerSCADA Expert v8.1 and PowerSCADA Expert v8.2 and Citect Anywhere version 1.0 that al…
CVE-2017-7970USmedium6.5—
A vulnerability exists in Schneider Electric's PowerSCADA Anywhere v1.0 redistributed with PowerSCADA Expert v8.1 and PowerSCADA Expert v8.2 and Citect Anywhere version 1.0 that al…
CVE-2017-7969UShigh8.8—
A cross-site request forgery vulnerability exists on the Secure Gateway component of Schneider Electric's PowerSCADA Anywhere v1.0 redistributed with PowerSCADA Expert v8.1 and Pow…
02

references

External citations — patches, advisories, analysis.

03

remediations (8)

  • MitigationCitect Anywhere

    Configure the HTTP origin header whitelist to match the environment's URL(s) used for accessing the secure gateway. This address may be one or more of the IP, machine name, or domain name where the secure gateway is hosted. The address may also be that of a load balancer or proxy, if the secure gateway is deployed that way.

  • MitigationCitect Anywhere

    Configure the HTTP origin header whitelist to match the environment's URL(s) used for accessing the secure gateway. This address may be one or more of the IP, machine name, or domain name where the secure gateway is hosted. The address may also be that of a load balancer or proxy, if the secure gateway is deployed that way.

  • MitigationCitect Anywhere

    Configure the HTTP origin header whitelist to match the environment's URL(s) used for accessing the secure gateway. This address may be one or more of the IP, machine name, or domain name where the secure gateway is hosted. The address may also be that of a load balancer or proxy, if the secure gateway is deployed that way.

  • MitigationCitect Anywhere

    Configure the HTTP origin header whitelist to match the environment's URL(s) used for accessing the secure gateway. This address may be one or more of the IP, machine name, or domain name where the secure gateway is hosted. The address may also be that of a load balancer or proxy, if the secure gateway is deployed that way.

  • MitigationPowerSCADA Anywhere redistributed with PowerSCADA Expert v8.1 and PowerSCADA Expert v8.2

    Configure the HTTP origin header whitelist to match the environment's URL(s) used for accessing the secure gateway. This address may be one or more of the IP, machine name, or domain name where the secure gateway is hosted. The address may also be that of a load balancer or proxy, if the secure gateway is deployed that way.

  • MitigationPowerSCADA Anywhere redistributed with PowerSCADA Expert v8.1 and PowerSCADA Expert v8.2

    Configure the HTTP origin header whitelist to match the environment's URL(s) used for accessing the secure gateway. This address may be one or more of the IP, machine name, or domain name where the secure gateway is hosted. The address may also be that of a load balancer or proxy, if the secure gateway is deployed that way.

  • MitigationPowerSCADA Anywhere redistributed with PowerSCADA Expert v8.1 and PowerSCADA Expert v8.2

    Configure the HTTP origin header whitelist to match the environment's URL(s) used for accessing the secure gateway. This address may be one or more of the IP, machine name, or domain name where the secure gateway is hosted. The address may also be that of a load balancer or proxy, if the secure gateway is deployed that way.

  • MitigationPowerSCADA Anywhere redistributed with PowerSCADA Expert v8.1 and PowerSCADA Expert v8.2

    Configure the HTTP origin header whitelist to match the environment's URL(s) used for accessing the secure gateway. This address may be one or more of the IP, machine name, or domain name where the secure gateway is hosted. The address may also be that of a load balancer or proxy, if the secure gateway is deployed that way.

scry

Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.

Free scan