Code execution via unchecked WCP field length
Published Nov 22, 2021 · Updated Sep 16, 2024
Stack-based buffer overflow in WECON PLC Editor 1.3.8 and earlier allows remote attackers to execute code via crafted WCP files. The WCP parser copies user-supplied data into a stack buffer without validating its length, allowing memory corruption in the current process. Exploitation requires the target to open a malicious file or visit a malicious page, and successful code runs with the application's privileges.
Summary
What happened
Stack-based buffer overflow in WECON PLC Editor 1.3.8 and earlier allows remote attackers to execute code via crafted WCP files. The WCP parser copies user-supplied data into a stack buffer without validating its length, allowing memory corruption in the current process. Exploitation requires the target to open a malicious file or visit a malicious page, and successful code runs with the application's privileges.
The record
- CVE
- CVE-2021-42705
- Published
- Nov 22, 2021
- Updated
- Sep 16, 2024
- Vendor
- WECON Technology Co., Ltd.
- Product
- PLC Editor
- Classifications
- CWE-121, T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 22, 2021CVE publishedPublication date reported by the CVE source.
- Sep 16, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=All <=1.3.8
What conditions does exploitation require?
What is affected?
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