# CVE-2025-0415: Command Injection in NTP Setting

> Remote administrators can execute arbitrary commands via NTP settings, potentially causing device reboot loops and network outages.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Apr 2025
- **Updated:** 3 Apr 2025
- **Also known as:** GHSA-mpp3-j837-w9p4

## What is CVE-2025-0415?

CVE-2025-0415 is a critical command injection vulnerability in Moxa EDF-G1002-BP Series, published on 2 Apr 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A remote attacker with web administrator privileges can exploit the device’s web interface to execute arbitrary system commands through the NTP settings. Successful exploitation may result in the device entering an infinite reboot loop, leading to a total or partial denial of connectivity for downstream systems that rely on its network services.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2025-0415?


## How do I fix CVE-2025-0415?

No fix has been published for CVE-2025-0415 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-0415 being exploited?

There is no known exploitation of CVE-2025-0415 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-0415 and fix it if it is affected.

What it is: CVE-2025-0415 is a critical command injection vulnerability in Moxa EDF-G1002-BP Series, published on 2 Apr 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-0415 in the wild and no public exploit code.

Affected product: Moxa EDF-G1002-BP Series. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-0415/ (Markdown: https://insights.sbomify.com/CVE-2025-0415/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-0415
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-0415
- OSV: https://osv.dev/vulnerability/CVE-2025-0415

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-0415/
Summaries are generated and may contain mistakes; the official description above is the record.