vendor:
Schneider Electric PLCs
by:
t4rkd3vilz
7.5
CVSS
HIGH
Cross-Site Request Forgery
352
CWE
Product Name: Schneider Electric PLCs
Affected Version From: Schneider Electric Quantum PLC: 140NOE77111, 140NOE77101, 140NWM10000, Modicon M340 PLC: BMXNOC0401, BMXNOE0100x, BMXNOE011xx, Premium PLC: TSXETY4103, TSXETY5103, and TSXWMY100
Affected Version To: Schneider Electric Quantum PLC: 140NOE77111, 140NOE77101, 140NWM10000, Modicon M340 PLC: BMXNOC0401, BMXNOE0100x, BMXNOE011xx, Premium PLC: TSXETY4103, TSXETY5103, and TSXWMY100
Patch Exists: YES
Related CWE: CVE-2013-0663
CPE: Schneider Electric Quantum PLC: 140NOE77111, 140NOE77101, 140NWM10000, Modicon M340 PLC: BMXNOC0401, BMXNOE0100x, BMXNOE011xx, Premium PLC: TSXETY4103, TSXETY5103, and TSXWMY100
Metasploit:
N/A
Other Scripts:
N/A
Platforms Tested: Windows
2018
Schneider Electric PLCs – Cross-Site Request Forgery
Schneider Electric PLCs are vulnerable to Cross-Site Request Forgery (CSRF) attacks. An attacker can craft a malicious HTML page that contains a form with pre-filled values. When a user visits the malicious page, the form is automatically submitted and the user's credentials are changed without their knowledge. This can be used to gain access to the PLCs.
Mitigation:
The best way to mitigate CSRF attacks is to use a combination of server-side and client-side security measures. On the server-side, the application should use a secret token to verify that the request is coming from a trusted source. On the client-side, the application should use a CAPTCHA to verify that the user is a human. Additionally, the application should use HTTPS to encrypt all communications.