Code execution via iocheckd cache parsing
Published Mar 11, 2020 · Updated Aug 4, 2024
A stack buffer overflow in WAGO PFC200 Firmware 03.02.02(14) allows local users to execute code via a crafted I/O-Check cache file and packet. The iocheckd service parses /tmp/iocheckCache.xml, which is globally writable, and copies attacker-controlled XML parameters into stack buffers when processing a BC_SaveParameter message. Exploitation requires the ability to write the cache file and reach the controller's I/O-Check service; successful exploitation can compromise confidentiality, integrity, and availability.
Summary
What happened
A stack buffer overflow in WAGO PFC200 Firmware 03.02.02(14) allows local users to execute code via a crafted I/O-Check cache file and packet. The iocheckd service parses /tmp/iocheckCache.xml, which is globally writable, and copies attacker-controlled XML parameters into stack buffers when processing a BC_SaveParameter message. Exploitation requires the ability to write the cache file and reach the controller's I/O-Check service; successful exploitation can compromise confidentiality, integrity, and availability.
The record
- CVE
- CVE-2019-5179
- Published
- Mar 11, 2020
- Updated
- Aug 4, 2024
- Vendor
- WAGO
- Product
- WAGO PFC200
- Classifications
- CWE-787
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 11, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Firmware version 03.02.02(14)
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