# CVE-2019-15498: Command injection in n/a

> Remote unauthenticated attackers can execute arbitrary OS commands on Vera Edge Home Controller devices via argument injection in the webcam script.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 23 Aug 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-v5m2-rjh8-pc69

## What is CVE-2019-15498?

CVE-2019-15498 is a high-severity command injection vulnerability in n/a, published on 23 Aug 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

cgi-bin/cmh/webcam.sh in Vera Edge Home Controller 1.7.4452 allows remote unauthenticated users to execute arbitrary OS commands via --output argument injection in the username parameter to /cgi-bin/cmh/webcam.sh.

Weakness: CWE-88 (Improper Neutralization of Argument Delimiters in a Command)

## Which versions are affected by CVE-2019-15498?

It affects 1 product.


Products: Getvera Vera Edge Firmware.

## How do I fix CVE-2019-15498?

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

## Is CVE-2019-15498 being exploited?

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

## Other vulnerabilities in n/a

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-15498 and fix it if it is affected.

What it is: CVE-2019-15498 is a high-severity command injection vulnerability in n/a, published on 23 Aug 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-15498 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-2019-15498/ (Markdown: https://insights.sbomify.com/CVE-2019-15498/index.md)
```

## Sources

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

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