Server crash via unchecked ACSE message buffer
Published Jan 14, 2022 · Updated Aug 4, 2024
NULL pointer dereference in libiec61850 1.5.0 allows remote attackers to crash an IEC 61850 server via a crafted ACSE message. AcseConnection_parseMessage reads buffer[0] at src/mms/iso_acse/acse.c:429 without first establishing that the message buffer is non-NULL. An unauthenticated TCP connection to the listening server is sufficient, and exploitation terminates the hosting process without reported data disclosure or modification.
Summary
What happened
NULL pointer dereference in libiec61850 1.5.0 allows remote attackers to crash an IEC 61850 server via a crafted ACSE message. AcseConnection_parseMessage reads buffer[0] at src/mms/iso_acse/acse.c:429 without first establishing that the message buffer is non-NULL. An unauthenticated TCP connection to the listening server is sufficient, and exploitation terminates the hosting process without reported data disclosure or modification.
The record
- CVE
- CVE-2021-45769
- Published
- Jan 14, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 14, 2022CVE 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
- Upstream base64 crash payloadproof 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