CVE-2025-6370
BaseFortify
Publication date: 2025-06-20
Last updated on: 2025-06-25
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| dlink | dir-619l_firmware | 2.06b1 |
| dlink | dir-619l | * |
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-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?
This vulnerability is a critical stack-based buffer overflow found in the D-Link DIR-619L 2.06B01 device. It occurs in the function formWlanGuestSetup within the file /goform/formWlanGuestSetup. The issue arises from manipulation of the argument curTime, which can be exploited remotely to cause the overflow. The vulnerability has been publicly disclosed and may be exploited. It affects only products that are no longer supported by the maintainer.
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to a stack-based buffer overflow, which may allow an attacker to execute arbitrary code remotely on the affected device. This can compromise the device's confidentiality, integrity, and availability, potentially leading to unauthorized access, data theft, or disruption of network services.
What immediate steps should I take to mitigate this vulnerability?
Since the affected products are no longer supported by the maintainer, immediate mitigation steps include disabling remote access to the vulnerable function if possible, restricting network access to the device, and replacing the affected device with a supported model to avoid exploitation.