Service crash via null-pointer read in ACSE parser
Published Sep 30, 2021 · Updated Aug 4, 2024
Denial of service in libiec_iccp_mod 1.5 allows remote attackers to crash server_example1 via a crafted ICCP message. AcseConnection_parseMessage dereferences a null address while parsing the message on a TCP connection. Exploitation requires network reachability and user interaction; successful delivery aborts the example server and interrupts its ICCP service.
Summary
What happened
Denial of service in libiec_iccp_mod 1.5 allows remote attackers to crash server_example1 via a crafted ICCP message. AcseConnection_parseMessage dereferences a null address while parsing the message on a TCP connection. Exploitation requires network reachability and user interaction; successful delivery aborts the example server and interrupts its ICCP service.
The record
- CVE
- CVE-2020-20664
- Published
- Sep 30, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 30, 2021CVE 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
- crash.zip proof of conceptproof of concept · demonstrated
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