Unauthenticated code execution via RK512 commands
Published Feb 20, 2023 · Updated Mar 18, 2025
Missing authentication in SICK FX0-GPNT v3 firmware 3.04 and 3.05 allows remote attackers to execute code through TCP port 9000. The RK512 configuration listener accepts crafted commands without authenticating the sender. Network access to the exposed listener is sufficient to alter gateway operation, cause permanent denial of service, or execute arbitrary code.
Summary
What happened
Missing authentication in SICK FX0-GPNT v3 firmware 3.04 and 3.05 allows remote attackers to execute code through TCP port 9000. The RK512 configuration listener accepts crafted commands without authenticating the sender. Network access to the exposed listener is sufficient to alter gateway operation, cause permanent denial of service, or execute arbitrary code.
The record
- CVE
- CVE-2023-23452
- Published
- Feb 20, 2023
- Updated
- Mar 18, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-306, T1210
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 20, 2023CVE publishedPublication date reported by the CVE source.
- Mar 18, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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