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

> Attackers can execute arbitrary commands on KERUI Wifi Endoscope Cameras due to missing authentication and improper input validation in the SSID setting.

- **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 Oct 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-4877-9vhq-rjr7

## What is CVE-2018-13114?

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

### Official description

Missing authentication and improper input validation in KERUI Wifi Endoscope Camera (YPC99) allow an attacker to execute arbitrary commands (with a length limit of 19 characters) via the "ssid" value, as demonstrated by ssid:;ping 192.168.1.2 in the body of a SETSSID command.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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

It affects 1 product.


Products: Keruigroup Ypc99 Firmware.

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

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

## Is CVE-2018-13114 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-13115](https://insights.sbomify.com/CVE-2018-13115/): Missing authorization in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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