Unauthenticated service interruption via crafted DNP3 message
Published Apr 15, 2020 · Updated Aug 4, 2024
Stack-based buffer overflow in Triangle MicroWorks DNP3 Outstation Libraries 3.16.00 through 3.25.01 allows remote attackers to interrupt service. The public advisory identifies a specially crafted DNP3 message as the trigger but does not disclose the parsing routine or stack-write operation. No authentication or user interaction is required; network access to an outstation endpoint is the exposure gate.
Summary
What happened
Stack-based buffer overflow in Triangle MicroWorks DNP3 Outstation Libraries 3.16.00 through 3.25.01 allows remote attackers to interrupt service. The public advisory identifies a specially crafted DNP3 message as the trigger but does not disclose the parsing routine or stack-write operation. No authentication or user interaction is required; network access to an outstation endpoint is the exposure gate.
The record
- CVE
- CVE-2020-6996
- Published
- Apr 15, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, CWE-121, T0866, T0814
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 15, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo