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

> Attackers can execute arbitrary OS commands via the web-interface PING feature in Cerio DT-300N devices, leading to full device compromise.

- **Severity:** High 8.8 (`CVSS:3.0/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:** 18 Jun 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-w8wc-95f8-wmh9

## What is CVE-2018-18852?

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

### Official description

Cerio DT-300N 1.1.6 through 1.1.12 devices allow OS command injection because of improper input validation of the web-interface PING feature's use of Save.cgi to execute a ping command, as exploited in the wild in October 2018.

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

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

It affects 1 product.


Products: Cerio Dt-300n Firmware.

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

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

## Is CVE-2018-18852 being exploited?

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

Public exploit code:

- CERIO RCE CVE-2018-18852, authenticated (vendor defaults) web-based RCE as root user. (github_poc): https://github.com/hook-s3c/CVE-2018-18852
- CERIO RCE CVE-2018-18852, authenticated (vendor defaults) web-based RCE as root user. (github_poc): https://github.com/andripwn/CVE-2018-18852

## Fix prompt for AI coding agents

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

What it is: CVE-2018-18852 is a high-severity command injection vulnerability in n/a, published on 18 Jun 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-2018-18852 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-18852/ (Markdown: https://insights.sbomify.com/CVE-2018-18852/index.md)
```

## Sources

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

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