Device damage via command injection
Published Jan 26, 2022 · Updated Aug 4, 2024
Command injection in Moxa TN-5900 firmware 3.1 and earlier allows remote attackers to execute malicious code and damage the device. Moxa has not disclosed the affected interface, parameter, or firmware routine that passes untrusted input to command execution. Network access without authentication or user interaction is sufficient; the documented consequence is device damage.
Summary
What happened
Command injection in Moxa TN-5900 firmware 3.1 and earlier allows remote attackers to execute malicious code and damage the device. Moxa has not disclosed the affected interface, parameter, or firmware routine that passes untrusted input to command execution. Network access without authentication or user interaction is sufficient; the documented consequence is device damage.
The record
- CVE
- CVE-2021-46560
- Published
- Jan 26, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-77, T1059
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 26, 2022CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record 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