CVE-2014-125117
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-07-25

Last updated on: 2025-09-23

Assigner: VulnCheck

Description
A stack-based buffer overflow vulnerability in the my_cgi.cgi component of certain D-Link devices, including the DSP-W215 version 1.02, can be exploited via a specially crafted HTTP POST request to the /common/info.cgi endpoint. This flaw enables an unauthenticated attacker to achieve remote code execution with system-level privileges.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-07-25
Last Modified
2025-09-23
Generated
2026-05-07
AI Q&A
2025-07-25
EPSS Evaluated
2026-05-05
NVD
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
dlink dsp-w215_firmware 1.02
dlink dsp-w215 *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-20 The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
CWE-121 A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

CVE-2014-125117 is a critical stack-based buffer overflow vulnerability in the my_cgi.cgi component of certain D-Link devices, notably the DSP-W215 version 1.02. The vulnerability occurs when the device improperly processes specially crafted HTTP POST requests to the /common/info.cgi endpoint, specifically in the handling of the 'storage_path' parameter. The POST data is parsed into a large stack-allocated buffer without proper bounds checking, allowing an attacker to overflow this buffer and overwrite the saved return address on the stack. By overwriting this return address with the address of the system() function, an unauthenticated attacker can remotely execute arbitrary commands on the device with system-level privileges. [1, 2, 3, 4]


How can this vulnerability impact me? :

This vulnerability allows an unauthenticated remote attacker to execute arbitrary code on affected D-Link devices with system-level privileges. This means the attacker can take full control of the device remotely without any user interaction or authentication. Potential impacts include unauthorized access, device compromise, disruption of device functionality, and use of the device as a foothold for further attacks within a network. [1, 2, 4]


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability can be detected by checking if the target device is a D-Link DSP-W215 running firmware version 1.02, which can be done by sending a GET request to the /common/info.cgi endpoint and inspecting the response for the strings "DSP-W215A1" and firmware version "1.02". Additionally, detection can involve attempting to send a crafted POST request to /common/info.cgi with the storage_path parameter to test for the buffer overflow condition. A practical approach is to use the Metasploit module for CVE-2014-125117, which includes automatic target detection by performing the GET request and verifying the device model and firmware version. Example commands include using curl or wget to fetch /common/info.cgi and grep for the identifying strings, or using the Metasploit framework module to automate detection and exploitation. [2, 4]


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include restricting network access to the vulnerable D-Link devices, especially blocking external HTTP POST requests to the /common/info.cgi endpoint to prevent exploitation. If possible, update the device firmware to a version that patches this vulnerability. If no patch is available, consider disabling or isolating the affected device from untrusted networks. Monitoring network traffic for suspicious POST requests targeting /common/info.cgi with unusually large payloads in the storage_path parameter can help detect exploitation attempts. Applying network-level firewall rules to block or limit access to the device's management interfaces is also recommended. [1, 3, 4]


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart