Client crash via unchecked null control object
Published Apr 13, 2023 · Updated Feb 7, 2025
NULL-pointer dereference in MZ Automation libiec61850 1.5.1 allows remote attackers to crash the bundled example client process. The example passes a null result from ControlObjectClient_create to ControlObjectClient_setOrigin without checking whether the requested control object exists. Reachability requires the example client to connect to a server lacking its hard-coded control object; the demonstrated consequence is limited to that client process crashing.
Summary
What happened
NULL-pointer dereference in MZ Automation libiec61850 1.5.1 allows remote attackers to crash the bundled example client process. The example passes a null result from ControlObjectClient_create to ControlObjectClient_setOrigin without checking whether the requested control object exists. Reachability requires the example client to connect to a server lacking its hard-coded control object; the demonstrated consequence is limited to that client process crashing.
The record
- CVE
- CVE-2023-27772
- Published
- Apr 13, 2023
- Updated
- Feb 7, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-754, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 13, 2023CVE publishedPublication date reported by the CVE source.
- Feb 7, 2025Record 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
- Issue 442 reproduction procedureproof 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