# CVE-2019-9122: Command injection in n/a

> Remote attackers can execute arbitrary commands on D-Link DIR-825 routers via the ntp_server parameter in an NTP sync request.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Feb 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-4ww3-7pf6-6cmg

## What is CVE-2019-9122?

CVE-2019-9122 is a high-severity command injection vulnerability in n/a, published on 25 Feb 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered on D-Link DIR-825 Rev.B 2.10 devices. They allow remote attackers to execute arbitrary commands via the ntp_server parameter in an ntp_sync.cgi POST request.

## Which versions are affected by CVE-2019-9122?

It affects 1 product.


Products: Dlink Dir-825 Rev.b Firmware.

## How do I fix CVE-2019-9122?

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

## Is CVE-2019-9122 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-9123](https://insights.sbomify.com/CVE-2019-9123/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2019-9126](https://insights.sbomify.com/CVE-2019-9126/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-9122 and fix it if it is affected.

What it is: CVE-2019-9122 is a high-severity command injection vulnerability in n/a, published on 25 Feb 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-9122 in the wild and no public exploit code.

Affected product: n/a. 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-2019-9122/ (Markdown: https://insights.sbomify.com/CVE-2019-9122/index.md)
```

## Sources

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

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