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

> Attackers can execute arbitrary OS commands on Foscam cameras by injecting shell metacharacters into the modelName parameter via a writable configuration file.

- **Severity:** High 7.2 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Nov 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-94wf-ph32-ggm2

## What is CVE-2018-19073?

CVE-2018-19073 is a high-severity command injection vulnerability in n/a, published on 7 Nov 2018. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An issue was discovered on Foscam C2 devices with System Firmware 1.11.1.8 and Application Firmware 2.72.1.32, and Opticam i5 devices with System Firmware 1.5.2.11 and Application Firmware 2.21.1.128. They allow attackers to execute arbitrary OS commands via shell metacharacters in the modelName, by leveraging /mnt/mtd/app/config/ProductConfig.xml write access.

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

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

It affects 4 products.


Products: Foscam C2 Application Firmware, Foscam C2 System Firmware, Opticam I5 Application Firmware, Opticam I5 System Firmware.

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

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

## Is CVE-2018-19073 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-19063](https://insights.sbomify.com/CVE-2018-19063/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2018-19064](https://insights.sbomify.com/CVE-2018-19064/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2018-19067](https://insights.sbomify.com/CVE-2018-19067/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2018-19069](https://insights.sbomify.com/CVE-2018-19069/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2018-19076](https://insights.sbomify.com/CVE-2018-19076/): Auth bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-19073 is a high-severity command injection vulnerability in n/a, published on 7 Nov 2018. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-19073 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-19073/ (Markdown: https://insights.sbomify.com/CVE-2018-19073/index.md)
```

## Sources

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

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