Service interruption via network-induced CPU exhaustion
Published Jun 4, 2025 · Updated Jun 4, 2025
Uncontrolled resource consumption in Phoenix Contact ILC 1x1 ETH firmware allows remote attackers to interrupt PLC operation via network flooding. The controller spends so much CPU time handling high-volume network traffic that its IEC 61131 processing program slows or stops. No authentication is required; automation functions recover after the traffic load is removed, so the interruption is temporary rather than persistent.
Summary
What happened
Uncontrolled resource consumption in Phoenix Contact ILC 1x1 ETH firmware allows remote attackers to interrupt PLC operation via network flooding. The controller spends so much CPU time handling high-volume network traffic that its IEC 61131 processing program slows or stops. No authentication is required; automation functions recover after the traffic load is removed, so the interruption is temporary rather than persistent.
The record
- CVE
- CVE-2018-25112
- Published
- Jun 4, 2025
- Updated
- Jun 4, 2025
- Vendor
- Phoenix Contact
- Product
- ILC 171 ETH 2TX
- Classifications
- CWE-770, T1499.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 4, 2025CVE publishedPublication date reported by the CVE source.
- Jun 4, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=vers:all/*
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
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