CVE-2020-6996:

Stack-based buffer overflow vulnerability in Triangle MicroWorks DNP3 Outstation Libraries allows remote attackers to potentially execute arbitrary code without authentication.

Score
A numerical rating that indicates how dangerous this vulnerability is.

9.8Critical

Published Date:Apr 15, 2020
CISA KEV Date:*No Data*
Industries Affected:20

Threat Predictions

EPSS Score:0.4
EPSS Percentile:58%

Exploitability

Score:3.9
Attack Vector:NETWORK
Attack Complexity:LOW
Privileges Required:NONE
User Interaction:NONE
Scope:UNCHANGED

Impact

Score:5.9
Confidentiality Impact:HIGH
Integrity Impact:HIGH
Availability Impact:HIGH

Description Preview

Stack-based buffer overflow vulnerability in Triangle MicroWorks DNP3 Outstation Libraries allows remote attackers to potentially execute arbitrary code without authentication.

Overview

The vulnerability exists in Triangle MicroWorks DNP3 Outstation Libraries, which are commonly used in industrial control systems for communication using the DNP3 protocol. The affected versions (3.16.00 through 3.25.01) contain a stack-based buffer overflow vulnerability that could allow an attacker to send specially crafted messages to trigger the overflow condition. Since no authentication is required to exploit this vulnerability, an attacker with network access to systems using these libraries could potentially execute arbitrary code, cause denial of service, or gain unauthorized access to the system. This vulnerability is particularly concerning for critical infrastructure sectors that rely on DNP3 protocol for SCADA communications, including electric utilities, water systems, and other industrial environments.

Remediation

1. Update to the latest version of Triangle MicroWorks DNP3 Outstation Libraries (version newer than 3.25.01) as provided by the vendor.
2. If immediate patching is not possible, implement network segmentation to isolate systems using the vulnerable libraries.
3. Monitor network traffic for unusual DNP3 protocol communications that might indicate exploitation attempts.
4. Implement access control lists and firewall rules to restrict access to DNP3 communication channels to trusted hosts only.
5. Consider implementing intrusion detection systems specifically configured to detect DNP3 protocol anomalies.
6. Follow defense-in-depth strategies by adding additional security layers around critical systems using these libraries.
7. Contact Triangle MicroWorks for specific mitigation guidance if you cannot update immediately.