PLC service interruption via unauthenticated safety-state request
Published Jun 30, 2025 · Updated Feb 16, 2026
Missing authentication in ifm Smart PLC AC4xxS firmware allows remote attackers to trigger its fail-safe state with a crafted HTTP request. An endpoint-hosted script accepts the safety-state request without authenticating the caller. Network reachability to the HTTP interface is sufficient, and exploitation interrupts PLC availability and can disrupt or damage a production line.
Summary
What happened
Missing authentication in ifm Smart PLC AC4xxS firmware allows remote attackers to trigger its fail-safe state with a crafted HTTP request. An endpoint-hosted script accepts the safety-state request without authenticating the caller. Network reachability to the HTTP interface is sufficient, and exploitation interrupts PLC availability and can disrupt or damage a production line.
The record
- CVE
- CVE-2024-8419
- Published
- Jun 30, 2025
- Updated
- Feb 16, 2026
- Vendor
- ifm electronic GmbH
- Product
- ifm AC432S
- Classifications
- CWE-306, T0814
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 30, 2025CVE publishedPublication date reported by the CVE source.
- Feb 16, 2026Record 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=4.04 <4.3.17
- Affected versionversion=6.1.8
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