# CVE-2018-6826: Code injection in n/a

> Man-in-the-middle attackers can execute arbitrary code on VOBOT CLOCK devices by intercepting cleartext HTTP requests during the Breakout Easter Egg feature launch.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:H/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:** 9 Feb 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-ccfq-q6wr-w5jc

## What is CVE-2018-6826?

CVE-2018-6826 is a high-severity code injection vulnerability in n/a, published on 9 Feb 2018. 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

An issue was discovered on VOBOT CLOCK before 0.99.30 devices. Cleartext HTTP is used to download a breakout program, and therefore man-in-the-middle attackers can execute arbitrary code by watching for a local user to launch the Breakout Easter Egg feature, and then sending a crafted HTTP response.

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

It affects 1 product.


Products: Omninova Vobot Firmware.

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

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

## Is CVE-2018-6826 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-6825](https://insights.sbomify.com/CVE-2018-6825/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2018-6827](https://insights.sbomify.com/CVE-2018-6827/): Weak cryptography in n/a (high 8.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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