CVE-2013-10050
BaseFortify
Publication date: 2025-08-01
Last updated on: 2025-09-23
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| dlink | dir-300_firmware | to 1.05 (inc) |
| dlink | dir-300 | a |
| dlink | dir-615_firmware | to 4.13 (inc) |
| dlink | dir-615 | d |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-78 | The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is an OS command injection flaw in multiple D-Link routers, specifically confirmed on DIR-300 rev A (v1.05) and DIR-615 rev D (v4.13). It occurs via the authenticated tools_vct.xgi CGI endpoint where the web interface does not properly sanitize user input in the pingIp parameter. This allows attackers with valid credentials to inject arbitrary shell commands, potentially leading to full device compromise including spawning a telnet daemon and gaining a root shell.
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to full compromise of the affected router device. An attacker with valid credentials can execute arbitrary shell commands, spawn a telnet daemon, and obtain a root shell, effectively gaining complete control over the device. This can result in unauthorized access, manipulation of network traffic, and potential further attacks on connected systems.
What immediate steps should I take to mitigate this vulnerability?
Since no vendor patch is available and affected models are end-of-life, immediate mitigation steps include restricting access to the router's web interface to trusted users only, disabling remote management if enabled, and avoiding use of the vulnerable tools_vct.xgi CGI endpoint. Additionally, consider replacing the affected devices with newer, supported models to eliminate the vulnerability.