# CVE-2018-9285: Command injection in n/a

> Attackers can execute arbitrary OS commands on ASUS routers via the pingCNT and destIP fields in the apply.cgi endpoint.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Apr 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-8g7r-fwgg-5qfg

## What is CVE-2018-9285?

CVE-2018-9285 is a critical command injection vulnerability in n/a, published on 4 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Main_Analysis_Content.asp in /apply.cgi on ASUS RT-AC66U, RT-AC68U, RT-AC86U, RT-AC88U, RT-AC1900, RT-AC2900, and RT-AC3100 devices before 3.0.0.4.384_10007; RT-N18U devices before 3.0.0.4.382.39935; RT-AC87U and RT-AC3200 devices before 3.0.0.4.382.50010; and RT-AC5300 devices before 3.0.0.4.384.20287 allows OS command injection via the pingCNT and destIP fields of the SystemCmd variable.

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

## Which versions are affected by CVE-2018-9285?

It affects 11 products.


Products: Asus Rt-Ac1900 Firmware, Asus Rt-Ac2900 Firmware, Asus Rt-Ac3100 Firmware, Asus Rt-Ac3200 Firmware, Asus Rt-Ac5300 Firmware, Asus Rt-Ac66u Firmware, Asus Rt-Ac68u Firmware, Asus Rt-Ac86u Firmware, Asus Rt-Ac87u Firmware, Asus Rt-Ac88u Firmware, Asus Rt-N18u Firmware.

## How do I fix CVE-2018-9285?

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

## Is CVE-2018-9285 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-9285 and fix it if it is affected.

What it is: CVE-2018-9285 is a critical command injection vulnerability in n/a, published on 4 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-9285 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-2018-9285/ (Markdown: https://insights.sbomify.com/CVE-2018-9285/index.md)
```

## Sources

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

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