Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
Configuration 1 [-]
| AND |
|
No data.
| Vendor | Product | Versions |
|---|---|---|
| D-link | Dcs-825l | — |
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2025-25614 | D-Link DCS-825L firmware version 1.08.01 and possibly prior versions contain an insecure implementation in the mydlink-watch-dog.sh script. The script monitors and respawns the `dcp` and `signalc` binaries without validating their integrity, origin, or permissions. An attacker with filesystem access (e.g., via UART or firmware modification) may replace these binaries to achieve persistent arbitrary code execution with root privileges. The issue stems from improper handling of executable trust and absence of integrity checks in the watchdog logic. |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.203% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Dlink
Dlink dcs-825l Dlink dcs-825l Firmware |
|
| CPEs | cpe:2.3:h:dlink:dcs-825l:-:*:*:*:*:*:*:* cpe:2.3:o:dlink:dcs-825l_firmware:*:*:*:*:*:*:*:* |
|
| Vendors & Products |
Dlink
Dlink dcs-825l Dlink dcs-825l Firmware |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
D-link
D-link dcs-825l |
|
| Vendors & Products |
D-link
D-link dcs-825l |
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-269 CWE-306 CWE-494 |
|
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | D-Link DCS-825L firmware version 1.08.01 and possibly prior versions contain an insecure implementation in the mydlink-watch-dog.sh script. The script monitors and respawns the `dcp` and `signalc` binaries without validating their integrity, origin, or permissions. An attacker with filesystem access (e.g., via UART or firmware modification) may replace these binaries to achieve persistent arbitrary code execution with root privileges. The issue stems from improper handling of executable trust and absence of integrity checks in the watchdog logic. | |
| References |
|