Summary
A critical OS command injection vulnerability affects the Boa web component in the Tenda HG10 router. A remote attacker may be able to manipulate the fmgpon_loid parameter and cause the device to execute operating-system commands when the vulnerable form handler processes the request.
Affected context
The vulnerability occurs in the formgponConf handler at /boaform/admin/formgponConf on affected Tenda HG10 firmware. Risk is present when the Boa web interface is reachable by an attacker and the handler incorporates the fmgpon_loid value into an operating-system command without adequate separation, validation, or escaping.
Exploit preconditions
- Attack surface: The Boa HTTP administration interface and its
formgponConfrequest handler - Required access: Network reachability to the exposed web service; authentication requirements depend on the device's access controls and deployment configuration
- Trigger point: Processing of the
fmgpon_loidargument - Why exploitation is possible: Attacker-controlled input reaches an operating-system command execution path without sufficient command isolation
- Scope: Remote exploitation is possible where the vulnerable management interface is accessible
Why this happens
The underlying bug is improper neutralization of special elements in externally supplied input used to construct or invoke an operating-system command. This behavior maps primarily to CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection'). CWE-77, which covers improper command construction, is also related because the application appears to combine untrusted parameter data with command-processing logic rather than treating the value strictly as data.
Potential impact
- An attacker may execute arbitrary commands with the privileges of the Boa service
- The device could be taken over or rendered unavailable
- Configuration, credentials, or network information could be exposed
- The compromised router could be used for lateral movement or additional attacks
- Device traffic could be monitored, redirected, or disrupted
General mitigation guidance
Mitigation generally focuses on removing shell interpretation from request-processing paths and reducing trust in administrative inputs.
Common defensive patterns include:
- Prefer direct APIs or fixed argument arrays instead of shell command construction
- Enforce strict allowlists and type-aware validation for configuration values
- Keep user-controlled data separate from executable command structure
- Restrict administrative interfaces to trusted management networks and require strong access controls
- Run web-management services with the least privileges necessary
- Apply network segmentation and disable unnecessary remote administration exposure
- Use read-only or constrained execution environments where practical
How teams detect issues like this
Organizations can look for command-injection risks through:
- Static analysis rules identifying request parameters passed to shell, process-spawn, or command-wrapper APIs
- Code review checks for string concatenation or interpolation involving HTTP parameters and system commands
- Tests that verify special characters are rejected or treated strictly as data
- Web-application firewall or gateway policies monitoring suspicious command metacharacters in administrative requests
- Device and network telemetry showing unexpected management requests, process launches, outbound connections, or configuration changes
- Automated security review tools that flag untrusted input reaching command-execution sinks

