# CVE-2018-6000: Missing authorization in n/a

> Unauthenticated attackers can set admin passwords and enable SSH via a crafted request in vpnupload.cgi, gaining remote administrative access.

- **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:** 22 Jan 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-92f5-6w73-42pg

## What is CVE-2018-6000?

CVE-2018-6000 is a critical missing authorization vulnerability in n/a, published on 22 Jan 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 AsusWRT before 3.0.0.4.384_10007. The do_vpnupload_post function in router/httpd/web.c in vpnupload.cgi provides functionality for setting NVRAM configuration values, which allows attackers to set the admin password and launch an SSH daemon (or enable infosvr command mode), and consequently obtain remote administrative access, via a crafted request. This is available to unauthenticated attackers in conjunction with CVE-2018-5999.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Asus Asuswrt.

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

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

## Is CVE-2018-6000 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-6000 exists.

Public exploit code:

- AsusWRT Router < 3.0.0.4.380.7743 - LAN Remote Code Execution (exploitdb)
- AsusWRT LAN Unauthenticated Remote Code Execution (metasploit)
- AsusWRT LAN - Remote Code Execution (Metasploit) (exploitdb)
- AsusWRT LAN - Remote Code Execution (Metasploit) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2018-20334](https://insights.sbomify.com/CVE-2018-20334/): Command injection in n/a (critical 9.8)
- [CVE-2018-5999](https://insights.sbomify.com/CVE-2018-5999/): Auth bypass in n/a (critical 9.8)
- [CVE-2017-15655](https://insights.sbomify.com/CVE-2017-15655/): Memory corruption in n/a (critical 9.6)
- [CVE-2017-15653](https://insights.sbomify.com/CVE-2017-15653/): Auth bypass in n/a (high 8.8)
- [CVE-2017-15656](https://insights.sbomify.com/CVE-2017-15656/): Hardcoded credentials in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-6000 is a critical missing authorization vulnerability in n/a, published on 22 Jan 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-6000 exists.

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-6000/ (Markdown: https://insights.sbomify.com/CVE-2018-6000/index.md)
```

## Sources

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

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