Summary
NUUO Network Video Recorder 2.0.0 contains a command injection vulnerability in
handle_import_privilege.php. If attacker-controlled input reaches this handler
without adequate separation from operating-system commands, an attacker may execute
commands with the privileges of the NVR service.
Affected context
The vulnerability occurs in the privilege-import functionality of NUUO Network
Video Recorder 2.0.0. Risk depends on whether the affected handler is reachable by
an attacker and whether imported privilege data or related request parameters can be
influenced without sufficient validation and command separation.
Exploit preconditions
- Attack surface: The NVR's privilege-import request handler,
handle_import_privilege.php
- Required access: Access sufficient to reach the affected functionality or
provide data processed by it; the exact access boundary depends on deployment
configuration
- Trigger point: Processing an import operation by the vulnerable handler
- Why exploitation is possible: Input may be incorporated into an operating-
system command without reliably treating it as data, allowing command syntax to
influence execution
Why this happens
The underlying bug is an operating-system command construction flaw. Data received
by the privilege-import handler can cross a trust boundary into a command interpreter
without robust separation, strict validation, or safe argument handling. This maps
to CWE-77: Improper Neutralization of Special Elements used in a Command, where
attacker-controlled values may alter the intended command rather than remain inert
data.
Potential impact
- An attacker could execute commands under the NVR service account
- The attacker may read, alter, or delete device data and configuration
- The NVR could be used to access connected systems or stored recordings
- Device availability could be disrupted
- Account or operational data could be modified
General mitigation guidance
Mitigation generally focuses on removing shell interpretation from application
workflows and reducing trust in imported privilege data.
Common defensive patterns include:
- Prefer direct library or system APIs over shell command construction
- Use fixed command and argument mappings rather than concatenated command strings
- Apply allowlist validation for privilege fields and imported values
- Treat uploaded or imported files as untrusted until validated against a strict schema
- Run the service with the minimum filesystem, process, and network privileges required
- Restrict access to administrative import functionality and protect it with strong
authentication and authorization
How teams detect issues like this
Detection can include static analysis for shell execution APIs, command strings built
through concatenation or interpolation, and request-derived values passed into process
execution functions. Code review should examine administrative import handlers,
archive or file-processing workflows, and validation performed before command
invocation. Runtime monitoring can flag unexpected child processes, shell launches,
or unusual command execution by the NVR service account. Automated security review
tools may help identify command-construction patterns during development.

