Unauthenticated command execution via logread type injection
Published May 2, 2023 · Updated Jul 9, 2026
OS command injection in GL.iNET MT3000 firmware 4.1.0 Release 2 allows remote attackers to execute arbitrary commands through logread RPC. The get_nginx_log handler inserts the request type into a command placeholder, allowing shell delimiters and following text to reach a Linux binary. No authentication or user interaction is required, and successful execution grants control of the router.
Summary
What happened
OS command injection in GL.iNET MT3000 firmware 4.1.0 Release 2 allows remote attackers to execute arbitrary commands through logread RPC. The get_nginx_log handler inserts the request type into a command placeholder, allowing shell delimiters and following text to reach a Linux binary. No authentication or user interaction is required, and successful execution grants control of the router.
The record
- CVE
- CVE-2023-29778
- Published
- May 2, 2023
- Updated
- Jul 9, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-78, T1059.004, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 2, 2023CVE publishedPublication date reported by the CVE source.
- Jul 9, 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?
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
- get_nginx_log_RCE proof of conceptproof of concept · demonstrated
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