CVE-2025-14140
BaseFortify
Publication date: 2025-12-06
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| utt | 520w_firmware | 1.7.7-180627 |
| utt | 520w | * |
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
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring HTTP requests to the /goform/websHostFilter endpoint for unusually long or malformed addHostFilter parameters that could trigger the buffer overflow. Network intrusion detection systems (NIDS) can be configured to alert on such suspicious requests. Specific commands are not provided in the resources, but inspecting HTTP traffic with tools like curl or tcpdump for requests to /goform/websHostFilter with large payloads in addHostFilter may help detect exploitation attempts. [1, 3]
Can you explain this vulnerability to me?
This vulnerability exists in the UTT θΏε 520W 1.7.7-180627 device, specifically in the strcpy function within the /goform/websHostFilter file. By manipulating the argument addHostFilter, an attacker can cause a buffer overflow. This overflow can be exploited remotely, potentially allowing an attacker to disrupt the device's normal operation or cause a denial of service.
How can this vulnerability impact me? :
The vulnerability can be exploited remotely to cause a buffer overflow, which may lead to denial of service or disruption of the affected device's functionality. Since the exploit is public, attackers could use it to impact the availability of the device or network relying on it.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the affected device's web interface, especially the /goform/websHostFilter endpoint, by implementing network-level access controls or firewall rules. Since no vendor patch or mitigation is available and the exploit is public, consider replacing the affected UTT θΏε 520W device with a secure alternative. Monitoring for exploitation attempts and isolating vulnerable devices from untrusted networks are also recommended. [3]