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

> Attackers can execute arbitrary commands on Guardzilla GZ180 devices via the remote upgrade feature's firmware version parameter.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/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:** 31 Dec 2018
- **Updated:** 6 May 2025
- **Also known as:** GHSA-mcwm-rp7p-mm3c

## What is CVE-2018-18600?

CVE-2018-18600 is a high-severity command injection vulnerability in n/a, published on 31 Dec 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The remote upgrade feature in Guardzilla GZ180 devices allow command injection via a crafted new firmware version parameter.

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

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

It affects 2 products.


Products: Guardzilla 180 Indoor Firmware, Guardzilla 180 Outdoor Firmware.

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

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

## Is CVE-2018-18600 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-18602](https://insights.sbomify.com/CVE-2018-18602/): Information disclosure in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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