CVE-2025-14709
Buffer Overflow in Shiguangwu sgwbox N3 Remote Exploitable
Publication date: 2025-12-15
Last updated on: 2025-12-15
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| shiguangwu | sgwbox_n3 | 2.0.25 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-119 | The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data. |
| CWE-120 | The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-14709 is a critical buffer overflow vulnerability in Shiguangwu sgwbox N3 version 2.0.25. It occurs in the WIRELESSCFGGET interface within the file /usr/sbin/http_eshell_server due to improper handling of the 'params' argument. Specifically, the input buffer is copied to an output buffer without verifying that the input size fits, leading to a classic buffer overflow (CWE-120). This flaw allows remote attackers to exploit the system without authentication, potentially compromising confidentiality, integrity, and availability. [1, 2]
How can this vulnerability impact me? :
This vulnerability can be exploited remotely without authentication, allowing attackers to cause a buffer overflow that may lead to system crashes or denial-of-service (DoS) conditions. It impacts the confidentiality, integrity, and availability of the affected system, potentially allowing attackers to disrupt services or gain unauthorized control. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
No patches or mitigations are currently known for this vulnerability. The vendor did not respond to the disclosure. The suggested immediate step is to replace the affected product to avoid exploitation. Monitoring for any suspicious activity targeting the WIRELESSCFGGET interface and restricting network access to the affected service may help reduce risk temporarily. [1]