Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach device Timezone Push Handler
-
ExploitCraft malicious tz argument
-
ExecutionTrigger command injection in iscm
-
ImpactExecute OS commands on router
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization OS command sanitization, avoid shell exec
MITRE ATT&CK
2 techniques across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The target must be a Qihoo 360 D603-2, D600-2, or D606-6 running firmware at or below 6.3.2, which lacks the check_timezone_parameter validation introduced in 6.4.0. Exploitation requires the attacker to deliver a push message whose tz argument reaches the on_push_message function in /fs2/bin/iscm (the Timezone Push Handler); shell metacharacters in that argument are then executed as OS commands. LIMITING FACTORS: only the three listed router models at/below 6.3.2 are affected, and the attacker must be able to reach the device's timezone push channel - the delivery path and whether that channel requires any cloud/account authentication are not described in the available sources, so the stated PR:N reachability is not independently confirmed. |
| Impact | Signals point to a real but non-emergency issue. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) describes a remotely reachable, low-complexity flaw with no authentication or user interaction, and exploit maturity is flagged E:P (proof-of-concept). The vuln.today priority is 'this_month', not act_now or emergency, and there is no CISA KEV listing and no EPSS score provided, so there is no evidence of active or widespread exploitation. A public PoC reference exists but is not verified as working exploit code, so exploitability should be treated as plausible rather than proven. Note a tension in the impact rating: VulDB scored impact as low across the board (VC:L/VI:L/VA:L) and the overall score 6.9, yet the flaw is OS command injection (CWE-78), a class that normally yields full arbitrary command execution - the privilege level of the /fs2/bin/iscm process is not stated in the sources, so the low impact rating cannot be independently reconciled and should be verified. Combined with a narrow, niche affected product set, this is a 'patch on a normal cycle' item rather than a drop-everything priority. |
| Exploit ScenarioDerived | A remote attacker who can deliver a crafted timezone push message to an affected Qihoo 360 router (D603-2, D600-2, D606-6 at or below 6.3.2) embeds shell metacharacters in the tz argument, which is processed by the on_push_message function in /fs2/bin/iscm without validation, resulting in OS command injection. A public PoC reference exists but is not verified as working exploit code. CVSS indicates low attack complexity and no required privileges, though the sources do not describe how the push channel is reached. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Nov 04, 2026
OS command injection in the Qihoo 360 D603-2, D600-2 and D606-6 router firmware at or below 6.3.2 allows remote attackers to run arbitrary shell commands on the device by supplying shell metacharacters in the tz argument handled by on_push_message in /fs2/bin/iscm. Only those three models on firmware up to 6.3.2 lack the check_timezone_parameter validation added in 6.4.0, and while the assessed vector is unauthenticated, the push-message delivery path and whether it requires cloud/account authentication are not described in the available sources, so that reachability is not independently confirmed. There is no CISA KEV listing, but a public PoC reference exists; it is not verified as working exploit code. The vendor-released patch is firmware 6.4.0.
RemediationAI
Vendor-released patch: firmware 6.4.0, which adds the check_timezone_parameter validation on the on_push_message path; upgrading the affected component is what the advisory advises, and no separate workaround or configuration fix is documented. In practical terms that means updating all three models (D603-2, D600-2, D606-6) still on 6.3.2 or below, tracking the advisory at https://vuldb.com/vuln/430445 for build availability per model. Because the timezone push channel's delivery path and authentication requirements are not described in the available sources, the only actionable interim control is to keep these devices off untrusted or internet-exposed segments and restrict which networks can reach the firmware's push/management interfaces, accepting that this may block legitimate cloud-driven timezone or configuration updates until 6.4.0 is installed. Treat the public PoC reference, though not verified as working exploit code, as a reason to schedule the upgrade in the current monthly patch window rather than defer it.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 3 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The affected component is the Timezone Push Handler inside /fs2/bin/iscm, the firmware binary that processes pushed configuration messages on 360 D-series routers. In the on_push_message function the tz argument is passed onward without sanitisation, so shell metacharacters embedded in that value are interpreted by the underlying OS command shell (CWE-78, OS Command Injection). VulDB's vulnerability analysis team disassembled firmware 6.4.0 and confirmed that the new build gates the same code path with a check_timezone_parameter validation, which indicates the root cause is the absence of an argument-sanitisation step on that specific parameter rather than a general input-handling redesign. The published CVSS 4.0 score of 6.9 with E:P reflects a proof-of-concept stage; our own assessment scores it higher (CVSS 3.1 AV:N/AC:L/PR:N/UI:N with C/I/A:H) because successful injection yields full command execution on the device, though that assumes the push channel is reachable without credentials. The trigger path beyond 'push message containing tz reaches on_push_message' is not described in the available sources.
Know when D603 2 gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
OS command injection yields arbitrary command execution, so C/I/A:H; AV:N/PR:N/UI:N per the remote, unauthenticated trigger described, though push-channel reachability is unverified.
Primary rating from Vendor (VulDB).
CVSS VectorVendor: VulDB
Lifecycle Timeline
2DescriptionCVE.org
A vulnerability was determined in Qihoo 360 D603-2, D600-2 and D606-6 up to 6.3.2. This vulnerability affects the function on_push_message of the file /fs2/bin/iscm of the component Timezone Push Handler. Executing a manipulation of the argument tz can lead to os command injection. The attack may be launched remotely. The exploit has been publicly disclosed and may be utilized. Upgrading to version 6.4.0 is able to resolve this issue. Upgrading the affected component is advised. Firmware 6.4.0 gates the path with a new check_timezone_parameter validation (verified by VulDB vulnerability analysis team via disassembly).
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
OS command injection occurs when an application passes unsanitized user input directly into system shell commands.
OS command injection in the testspeed_command function of /fs2/bin/iscm on Qihoo 360 D-series networking devices (D603-2
Qihoo 360 router firmware through 6.4.9 contains an improper cryptographic signature verification flaw in the verify_sig
EUVD-2026-116672
NVD
CVE.org
GitHub
VulDB
Exploit-DB