Local code execution via oversized cache type
Published Mar 11, 2020 · Updated Aug 4, 2024
Stack buffer overflow in WAGO PFC200 firmware 03.02.02(14) allows local users to execute code through a crafted XML cache file. The iocheckd parser inserts the attacker-controlled type node from /tmp/iocheckCache.xml into a 1,024-byte stack buffer with unbounded sprintf. A local user must first write the cache file and then trigger BC_SaveParameter over the controller protocol; successful exploitation corrupts control flow, while a 0x3d9-byte type value crashes the service.
Summary
What happened
Stack buffer overflow in WAGO PFC200 firmware 03.02.02(14) allows local users to execute code through a crafted XML cache file. The iocheckd parser inserts the attacker-controlled type node from /tmp/iocheckCache.xml into a 1,024-byte stack buffer with unbounded sprintf. A local user must first write the cache file and then trigger BC_SaveParameter over the controller protocol; successful exploitation corrupts control flow, while a 0x3d9-byte type value crashes the service.
The record
- CVE
- CVE-2019-5182
- Published
- Mar 11, 2020
- Updated
- Aug 4, 2024
- Vendor
- WAGO
- Product
- WAGO PFC200
- Classifications
- CWE-787, CWE-120, T1499.004
- 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?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- TALOS-2019-0963 XML cache 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