Unauthenticated device reconfiguration via hard-coded credentials
Published Aug 24, 2023 · Updated Jun 1, 2026
Use of hard-coded credentials in SICK AG LMS5xx firmware before 2.21 allows remote attackers to reconfigure or disrupt the device. The firmware contains hard-coded credentials usable through the Ethernet-accessible device interface; SICK has not disclosed their values or exact authentication locus. Network reachability is sufficient and no prior account or user interaction is required, enabling unauthorized settings changes and interruption of sensor functionality.
Summary
What happened
Use of hard-coded credentials in SICK AG LMS5xx firmware before 2.21 allows remote attackers to reconfigure or disrupt the device. The firmware contains hard-coded credentials usable through the Ethernet-accessible device interface; SICK has not disclosed their values or exact authentication locus. Network reachability is sufficient and no prior account or user interaction is required, enabling unauthorized settings changes and interruption of sensor functionality.
The record
- CVE
- CVE-2023-4419
- Published
- Aug 24, 2023
- Updated
- Jun 1, 2026
- Vendor
- SICK AG
- Product
- LMS5xx
- Classifications
- CWE-798, T1078
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 24, 2023CVE publishedPublication date reported by the CVE source.
- Jun 1, 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=0 <2.21
- Affected versionversion=0 <V2.21
What conditions does exploitation require?
What is affected?
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.
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