Authenticated command execution via unsanitized iface parameter
Published May 5, 2025 · Updated May 5, 2025
Command injection in NETGEAR RAX5 firmware 1.0.2.26 allows remote authenticated users to execute commands through a crafted iface value. The vif_enable route accepts iface from the URL path and treats shell separators in that value as commands. Exploitation requires a valid sysauth session and runs injected commands in the router web-management context.
Summary
What happened
Command injection in NETGEAR RAX5 firmware 1.0.2.26 allows remote authenticated users to execute commands through a crafted iface value. The vif_enable route accepts iface from the URL path and treats shell separators in that value as commands. Exploitation requires a valid sysauth session and runs injected commands in the router web-management context.
The record
- CVE
- CVE-2024-57235
- Published
- May 5, 2025
- Updated
- May 5, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-77, T1059
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 5, 2025CVE publishedPublication date reported by the CVE source.
- May 5, 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
- vif_enable HTTP command-injection proof of conceptfunctional · 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