Vulnerabilities > Trianglemicroworks > Scada Data Gateway
DATE | CVE | VULNERABILITY TITLE | RISK |
---|---|---|---|
2023-06-07 | CVE-2023-2186 | Use of Externally-Controlled Format String vulnerability in Trianglemicroworks Scada Data Gateway On Triangle MicroWorks' SCADA Data Gateway version <= v5.01.03, an unauthenticated attacker can send a specially crafted broadcast message including format string characters to the SCADA Data Gateway to perform unrestricted memory reads.An unauthenticated user can use this format string vulnerability to repeatedly crash the GTWWebMonitor.exe process to DoS the Web Monitor. | 9.8 |
2023-06-07 | CVE-2023-2187 | Unspecified vulnerability in Trianglemicroworks Scada Data Gateway On Triangle MicroWorks' SCADA Data Gateway version <= v5.01.03, an unauthenticated attacker can send broadcast events to any user via the WebMonitor.An unauthenticated user can use this vulnerability to forcefully log out of any currently logged-in user by sending a "password change event". | 5.3 |
2020-04-15 | CVE-2020-10615 | Out-of-bounds Write vulnerability in Trianglemicroworks Scada Data Gateway Triangle MicroWorks SCADA Data Gateway 3.02.0697 through 4.0.122, 2.41.0213 through 4.0.122 allows remote attackers cause a denial-of-service condition due to a lack of proper validation of the length of user-supplied data, prior to copying it to a fixed-length stack-based buffer. | 7.5 |
2020-04-15 | CVE-2020-10613 | Out-of-bounds Read vulnerability in Trianglemicroworks Scada Data Gateway Triangle MicroWorks SCADA Data Gateway 3.02.0697 through 4.0.122, 2.41.0213 through 4.0.122 allows remote attackers to disclose sensitive information due to the lack of proper validation of user-supplied data, which can result in a read past the end of an allocated structure. | 7.5 |
2020-04-15 | CVE-2020-10611 | Type Confusion vulnerability in Trianglemicroworks Scada Data Gateway Triangle MicroWorks SCADA Data Gateway 3.02.0697 through 4.0.122, 2.41.0213 through 4.0.122 allows remote attackers to execute arbitrary code due to the lack of proper validation of user-supplied data, which can result in a type confusion condition. | 9.8 |