CVE Vulnerabilities

CVE-2014-2342

Uncontrolled Resource Consumption

Published: May 30, 2014 | Modified: Oct 02, 2025
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
5 MEDIUM
AV:N/AC:L/Au:N/C:N/I:N/A:P
RedHat/V2
RedHat/V3
Ubuntu

Triangle MicroWorks SCADA Data Gateway before 3.00.0635 allows remote attackers to cause a denial of service (excessive data processing) via a crafted DNP3 packet.

Weakness

The product does not properly control the allocation and maintenance of a limited resource.

Affected Software

Name Vendor Start Version End Version
Scada_data_gateway Trianglemicroworks * 3.00.0633 (including)
Scada_data_gateway Trianglemicroworks 2.50 (including) 2.50 (including)
Scada_data_gateway Trianglemicroworks 2.50.0309 (including) 2.50.0309 (including)
Scada_data_gateway Trianglemicroworks 2.51 (including) 2.51 (including)
Scada_data_gateway Trianglemicroworks 2.53 (including) 2.53 (including)
Scada_data_gateway Trianglemicroworks 2.54.0515 (including) 2.54.0515 (including)
Scada_data_gateway Trianglemicroworks 2.54.0516 (including) 2.54.0516 (including)
Scada_data_gateway Trianglemicroworks 2.54.0517 (including) 2.54.0517 (including)
Scada_data_gateway Trianglemicroworks 2.54.0518 (including) 2.54.0518 (including)
Scada_data_gateway Trianglemicroworks 2.54.0528 (including) 2.54.0528 (including)
Scada_data_gateway Trianglemicroworks 2.54.0529 (including) 2.54.0529 (including)
Scada_data_gateway Trianglemicroworks 2.54.0536 (including) 2.54.0536 (including)
Scada_data_gateway Trianglemicroworks 2.54.0540 (including) 2.54.0540 (including)
Scada_data_gateway Trianglemicroworks 2.54.0544 (including) 2.54.0544 (including)
Scada_data_gateway Trianglemicroworks 2.54.0545 (including) 2.54.0545 (including)
Scada_data_gateway Trianglemicroworks 2.54.0552 (including) 2.54.0552 (including)
Scada_data_gateway Trianglemicroworks 2.54.0553 (including) 2.54.0553 (including)
Scada_data_gateway Trianglemicroworks 2.54.0558 (including) 2.54.0558 (including)
Scada_data_gateway Trianglemicroworks 2.54.0561 (including) 2.54.0561 (including)
Scada_data_gateway Trianglemicroworks 2.54.0562 (including) 2.54.0562 (including)
Scada_data_gateway Trianglemicroworks 2.54.0564 (including) 2.54.0564 (including)
Scada_data_gateway Trianglemicroworks 2.54.0565 (including) 2.54.0565 (including)
Scada_data_gateway Trianglemicroworks 2.54.0566 (including) 2.54.0566 (including)
Scada_data_gateway Trianglemicroworks 2.54.0567 (including) 2.54.0567 (including)
Scada_data_gateway Trianglemicroworks 2.54.0569 (including) 2.54.0569 (including)
Scada_data_gateway Trianglemicroworks 2.54.0570 (including) 2.54.0570 (including)
Scada_data_gateway Trianglemicroworks 2.54.0571 (including) 2.54.0571 (including)
Scada_data_gateway Trianglemicroworks 2.54.0572 (including) 2.54.0572 (including)
Scada_data_gateway Trianglemicroworks 2.54.0573 (including) 2.54.0573 (including)
Scada_data_gateway Trianglemicroworks 2.54.0574 (including) 2.54.0574 (including)
Scada_data_gateway Trianglemicroworks 2.54.0575 (including) 2.54.0575 (including)
Scada_data_gateway Trianglemicroworks 2.54.0576 (including) 2.54.0576 (including)
Scada_data_gateway Trianglemicroworks 2.54.0577 (including) 2.54.0577 (including)
Scada_data_gateway Trianglemicroworks 2.54.0578 (including) 2.54.0578 (including)
Scada_data_gateway Trianglemicroworks 2.54.0579 (including) 2.54.0579 (including)
Scada_data_gateway Trianglemicroworks 2.54.0580 (including) 2.54.0580 (including)
Scada_data_gateway Trianglemicroworks 2.54.0581 (including) 2.54.0581 (including)
Scada_data_gateway Trianglemicroworks 2.54.0582 (including) 2.54.0582 (including)
Scada_data_gateway Trianglemicroworks 2.54.0583 (including) 2.54.0583 (including)
Scada_data_gateway Trianglemicroworks 2.54.0584 (including) 2.54.0584 (including)
Scada_data_gateway Trianglemicroworks 2.54.0586 (including) 2.54.0586 (including)
Scada_data_gateway Trianglemicroworks 2.54.0587 (including) 2.54.0587 (including)
Scada_data_gateway Trianglemicroworks 2.54.0588 (including) 2.54.0588 (including)
Scada_data_gateway Trianglemicroworks 2.54.0589 (including) 2.54.0589 (including)
Scada_data_gateway Trianglemicroworks 2.54.0590 (including) 2.54.0590 (including)
Scada_data_gateway Trianglemicroworks 2.54.0591 (including) 2.54.0591 (including)
Scada_data_gateway Trianglemicroworks 2.54.0592 (including) 2.54.0592 (including)
Scada_data_gateway Trianglemicroworks 2.54.0594 (including) 2.54.0594 (including)
Scada_data_gateway Trianglemicroworks 2.54.0595 (including) 2.54.0595 (including)
Scada_data_gateway Trianglemicroworks 2.54.0596 (including) 2.54.0596 (including)
Scada_data_gateway Trianglemicroworks 2.54.0597 (including) 2.54.0597 (including)
Scada_data_gateway Trianglemicroworks 2.54.0598 (including) 2.54.0598 (including)
Scada_data_gateway Trianglemicroworks 2.54.0599 (including) 2.54.0599 (including)
Scada_data_gateway Trianglemicroworks 3.00 (including) 3.00 (including)
Scada_data_gateway Trianglemicroworks 3.00.0612 (including) 3.00.0612 (including)
Scada_data_gateway Trianglemicroworks 3.00.0615 (including) 3.00.0615 (including)
Scada_data_gateway Trianglemicroworks 3.00.0616 (including) 3.00.0616 (including)
Scada_data_gateway Trianglemicroworks 3.00.0630 (including) 3.00.0630 (including)

Potential Mitigations

  • Mitigation of resource exhaustion attacks requires that the target system either:

  • The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question.

  • The second solution is simply difficult to effectively institute – and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.

References