# CVE-2018-18319: Code injection in n/a

> An attacker on a trusted intranet can execute arbitrary commands via eval in Merlin.PHP, though the vendor considers this intended behavior.

- **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:** 15 Oct 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-8334-vxcw-m5x6

## What is CVE-2018-18319?

CVE-2018-18319 is a critical code injection vulnerability in n/a, published on 15 Oct 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in the Merlin.PHP component 0.6.6 for Asuswrt-Merlin devices. An attacker can execute arbitrary commands because api.php has an eval call, as demonstrated by the /6/api.php?function=command&class=remote&Cc='ls' URI. NOTE: the vendor indicates that Merlin.PHP is designed only for use on a trusted intranet network, and intentionally allows remote code execution

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 14 products.


Products: Asuswrt-Merlin Project Rt-Ac1900 Firmware, Asuswrt-Merlin Project Rt-Ac2900 Firmware, Asuswrt-Merlin Project Rt-Ac3100 Firmware, Asuswrt-Merlin Project Rt-Ac3200 Firmware, Asuswrt-Merlin Project Rt-Ac5300 Firmware, Asuswrt-Merlin Project Rt-Ac56u Firmware, Asuswrt-Merlin Project Rt-Ac66u B1 Firmware, Asuswrt-Merlin Project Rt-Ac68p Firmware, Asuswrt-Merlin Project Rt-Ac68u Firmware, Asuswrt-Merlin Project Rt-Ac68uf Firmware, Asuswrt-Merlin Project Rt-Ac86u Firmware, Asuswrt-Merlin Project Rt-Ac87 Firmware, Asuswrt-Merlin Project Rt-Ac88u Firmware, Asuswrt-Merlin Project Rt Ac1900p Firmware.

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

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

## Is CVE-2018-18319 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-18320](https://insights.sbomify.com/CVE-2018-18320/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-18319 is a critical code injection vulnerability in n/a, published on 15 Oct 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-18319 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-18319/ (Markdown: https://insights.sbomify.com/CVE-2018-18319/index.md)
```

## Sources

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

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