Unauthenticated service crash via stack argument race
Published Apr 25, 2025 · Updated Apr 25, 2025
Memory corruption in OpenPLC Runtime 3 through 64f9c11 allows remote attackers to crash the service via rapid TCP sessions. server.cpp passes a stack-allocated argument array to detached handleConnections threads, which can read it after the parent frame is reused or unavailable. Default listeners on ports 502 and 44818 expose the race without authentication, causing invalid reads, corrupted connection state, or a process crash.
Summary
What happened
Memory corruption in OpenPLC Runtime 3 through 64f9c11 allows remote attackers to crash the service via rapid TCP sessions. server.cpp passes a stack-allocated argument array to detached handleConnections threads, which can read it after the parent frame is reused or unavailable. Default listeners on ports 502 and 44818 expose the race without authentication, causing invalid reads, corrupted connection state, or a process crash.
The record
- CVE
- CVE-2025-46613
- Published
- Apr 25, 2025
- Updated
- Apr 25, 2025
- Vendor
- OpenPLC Project
- Product
- OpenPLC
- Classifications
- CWE-362, T0814
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 25, 2025CVE publishedPublication date reported by the CVE source.
- Apr 25, 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=0 <=64f9c11263229b019091e3c5a1896c184e0661a6
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