Sunday, December 29, 2024
HomeCyber Security NewsUnpatched Bugs in Mitsubishi Safety PLCs Let Hackers Perform Remote Attacks

Unpatched Bugs in Mitsubishi Safety PLCs Let Hackers Perform Remote Attacks

Published on

SIEM as a Service

The cybersecurity researchers at Nozomi Networks Labs have recently warned about five unpatched security vulnerabilities in the safety programmable logic controllers (PLCs) of Mitsubishi.

All these security flaws are associated with the implementation of the authentication of the MELSOFT communication protocol, it’s used to exchange data with the target devices.

Threat actors could exploit these vulnerabilities through brute-force attacks, unauthorized login to the CPU module, and denial-of-service (DoS) attacks to procure the legitimate user names that are manifested in the module.

- Advertisement - SIEM as a Service

The security analysts claimed that all these security flaws have affected several vendors and while analyzing the MELSOFT protocol they detected these vulnerabilities.

Here the MELSOFT protocol is used as the communication protocol for Mitsubishi PLCs and related software for GX Works3 workstations.

Over TCP port 5007 through a login/password pair the authentication using MELSOFT is implemented, which could be vulnerable to brute force attacks in some cases.

Mitsubishi MELSOFT Authentication Vulnerabilities

Here we have mentioned the Mitsubishi MELSOFT Authentication vulnerabilities with their respective CVE IDs and CVSS score below:-

  • Username Brute-force, it’s tracked as CVE-2021-20594 with a CVSS score of 5.9 out of 10.
  • Leaks of Password Equivalent Secrets, it’s tracked as CVE-2021-20597 with a CVSS score of 7.4 out of 10.
  • Anti-password Brute-force Functionality Leads to Overly Restrictive Account Lockout Mechanism, it’s tracked as CVE-2021-20598 with a CVSS score of 3.7 out of 10.
  • Session Token Management.

Apart from this, the team of cybersecurity researchers at Nozomi Networks Labs have tested multiple methods that provide access to the systems, and they discovered that the threat actors can reuse the session tokens in come cases that are created after successful authentication.

At this stage, an attacker can easily block other users, once the attacker gain access to the system. As a result, it will lead them to manually disable the system by force simply to circumvent further risk.

Mitigations

Security analysts at Nozomi Networks Labs have recommended few general mitigations and here they are mentioned below:-

  • Make sure to secure the link between the engineering workstation and the PLC.
  • Also make sure to protect the MELSOFT authentication or authenticated packets in cleartext, so that an attacker couldn’t get access to them.
  • Make sure to secure access to the PLC to avoid any exploitations of authentication packets with the PLC.
  • Immediately change the PLC usernames.
  • Immediately change the PLC passwords.

Moreover, in order to protect the systems from potential attacks, the report presented by the researchers doesn’t specifically mention any technical details of the discovered vulnerabilities or any POC code for exploring them.

You can follow us on LinkedinTwitterFacebook for daily Cybersecurity, and hacking news updates.

Balaji
Balaji
BALAJI is an Ex-Security Researcher (Threat Research Labs) at Comodo Cybersecurity. Editor-in-Chief & Co-Founder - Cyber Security News & GBHackers On Security.

Latest articles

Lumma Stealer Attacking Users To Steal Login Credentials From Browsers

Researchers observed Lumma Stealer activity across multiple online samples, including PowerShell scripts and a...

New ‘OtterCookie’ Malware Attacking Software Developers Via Fake Job Offers

Palo Alto Networks reported the Contagious Interview campaign in November 2023, a financially motivated...

NjRat 2.3D Pro Edition Shared on GitHub: A Growing Cybersecurity Concern

The recent discovery of the NjRat 2.3D Professional Edition on GitHub has raised alarms...

Palo Alto Networks Vulnerability Puts Firewalls at Risk of DoS Attacks

A critical vulnerability, CVE-2024-3393, has been identified in the DNS Security feature of Palo...

API Security Webinar

72 Hours to Audit-Ready API Security

APIs present a unique challenge in this landscape, as risk assessment and mitigation are often hindered by incomplete API inventories and insufficient documentation.

Join Vivek Gopalan, VP of Products at Indusface, in this insightful webinar as he unveils a practical framework for discovering, assessing, and addressing open API vulnerabilities within just 72 hours.

Discussion points

API Discovery: Techniques to identify and map your public APIs comprehensively.
Vulnerability Scanning: Best practices for API vulnerability analysis and penetration testing.
Clean Reporting: Steps to generate a clean, audit-ready vulnerability report within 72 hours.

More like this

New ‘OtterCookie’ Malware Attacking Software Developers Via Fake Job Offers

Palo Alto Networks reported the Contagious Interview campaign in November 2023, a financially motivated...

NjRat 2.3D Pro Edition Shared on GitHub: A Growing Cybersecurity Concern

The recent discovery of the NjRat 2.3D Professional Edition on GitHub has raised alarms...

Palo Alto Networks Vulnerability Puts Firewalls at Risk of DoS Attacks

A critical vulnerability, CVE-2024-3393, has been identified in the DNS Security feature of Palo...